1.15-> 1.16. Perfectly clean remove and newly installed... But, there was a build error!

use for example https://pastebin.com to save well-formatted logs and then paste the link here

1. "C:\Amazon\Lumberyard\1.16.0.0\dev\lmbr_waf.bat" build_win_x64_vs2017_profile --enabled-game-projects=MyDefult1 -p MyDefult1
2. [WAF] Engine Root: C:\Amazon\Lumberyard\1.16.0.0\dev\
3. A custom BuildEnv.json file was not found. This build will be untagged.
4. A custom BuildEnv.json file was not found. This build will be untagged.
5. [WAF] Executing 'build_win_x64_vs2017_profile' in 'c:\Amazon\Lumberyard\1.16.0.0\dev\BinTemp\win_x64_vs2017_profile'
6. [WARN] Game folder 'StarterGame' configured in bootstrap.cfg is the enabled game for this build. In order to run or debug for the game 'MyDefult1', they need to be set in bootstrap.cfg under the 'sys_game_folder' entry accordingly
7. [WARNING] Incredibuild disabled by build option
8. [WARN] 3rd Party alias 'qt' specified in c:\Amazon\Lumberyard\1.16.0.0\dev\Code\Tools\Woodpecker\wscript:54 (build) is not enabled. Make sure that at least one of the following roles is enabled: []
9. [WARN] 3rd Party alias 'qt' specified in c:\Amazon\Lumberyard\1.16.0.0\dev\Code\Tools\Woodpecker\wscript:101 (build) is not enabled. Make sure that at least one of the following roles is enabled: []
10. unable to find QT
11. unable to find QT
12. Traceback (most recent call last):
13. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Scripting.py", line 226, in waf_entry_point
14. run_commands()
15. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Scripting.py", line 342, in run_commands
16. ctx = run_command(cmd_name)
17. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Scripting.py", line 319, in run_command
18. ctx.execute()
19. File ".\Tools\build\waf-1.7.13\lmbrwaflib\msvs.py", line 1949, in override_build_state
20. old(ctx)
21. File "c:\Amazon\Lumberyard\1.16.0.0\dev\wscript", line 469, in execute
22. return execute_method(self)
23. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Scripting.py", line 696, in execute
24. return execute_method(self)
25. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Build.py", line 254, in execute
26. self.execute_build()
27. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Build.py", line 277, in execute_build
28. self.compile()
29. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Build.py", line 370, in compile
30. self.producer.start()
31. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Runner.py", line 307, in start
32. self.refill_task_list()
33. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Runner.py", line 209, in refill_task_list
34. self.add_outstanding_tasks(next(self.biter))
35. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Build.py", line 818, in get_build_iterator
36. self.post_group()
37. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Build.py", line 789, in post_group
38. f()
39. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\TaskGen.py", line 218, in post
40. v()
41. File "Tools\build\waf-1.7.13\lmbrwaflib\cry_utils.py", line 893, in add_compiler_dependency
42. if os.path.isabs( self.env['CC'] ):
43. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\Python\2.7.12\windows\lib\ntpath.py", line 59, in isabs
44. return s != '' and s[:1] in '/\'
45. TypeError: 'in <string>' requires string as left operand, not list
46. Process failed with return code: 1
47. "C:\Amazon\Lumberyard\1.16.0.0\dev\lmbr_waf.bat" build_win_x64_vs2017_profile --enabled-game-projects=MyDefulat1 -p MyDefulat1
48. [WAF] Engine Root: C:\Amazon\Lumberyard\1.16.0.0\dev\
49. A custom BuildEnv.json file was not found. This build will be untagged.
50. A custom BuildEnv.json file was not found. This build will be untagged.
51. [WAF] Executing 'build_win_x64_vs2017_profile' in 'c:\Amazon\Lumberyard\1.16.0.0\dev\BinTemp\win_x64_vs2017_profile'
52. [WARN] Game folder 'StarterGame' configured in bootstrap.cfg is the enabled game for this build. In order to run or debug for the game 'MyDefulat1', they need to be set in bootstrap.cfg under the 'sys_game_folder' entry accordingly
53. [WARNING] Incredibuild disabled by build option
54. [WARN] 3rd Party alias 'qt' specified in c:\Amazon\Lumberyard\1.16.0.0\dev\Code\Tools\Woodpecker\wscript:54 (build) is not enabled. Make sure that at least one of the following roles is enabled: []
55. [WARN] 3rd Party alias 'qt' specified in c:\Amazon\Lumberyard\1.16.0.0\dev\Code\Tools\Woodpecker\wscript:101 (build) is not enabled. Make sure that at least one of the following roles is enabled: []
56. unable to find QT
57. unable to find QT
58. Traceback (most recent call last):
59. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Scripting.py", line 226, in waf_entry_point
60. run_commands()
61. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Scripting.py", line 342, in run_commands
62. ctx = run_command(cmd_name)
63. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Scripting.py", line 319, in run_command
64. ctx.execute()
65. File ".\Tools\build\waf-1.7.13\lmbrwaflib\msvs.py", line 1949, in override_build_state
66. old(ctx)
67. File "c:\Amazon\Lumberyard\1.16.0.0\dev\wscript", line 469, in execute
68. return execute_method(self)
69. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Scripting.py", line 696, in execute
70. return execute_method(self)
71. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Build.py", line 254, in execute
72. self.execute_build()
73. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Build.py", line 277, in execute_build
74. self.compile()
75. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Build.py", line 370, in compile
76. self.producer.start()
77. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Runner.py", line 307, in start
78. self.refill_task_list()
79. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Runner.py", line 209, in refill_task_list
80. self.add_outstanding_tasks(next(self.biter))
81. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Build.py", line 818, in get_build_iterator
82. self.post_group()
83. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\Build.py", line 789, in post_group
84. f()
85. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\build\waf-1.7.13\waflib\TaskGen.py", line 218, in post
86. v()
87. File "Tools\build\waf-1.7.13\lmbrwaflib\cry_utils.py", line 893, in add_compiler_dependency
88. if os.path.isabs( self.env['CC'] ):
89. File "C:\Amazon\Lumberyard\1.16.0.0\dev\Tools\Python\2.7.12\windows\lib\ntpath.py", line 59, in isabs
90. return s != '' and s[:1] in '/\'
91. TypeError: 'in <string>' requires string as left operand, not list
92. Process failed with return code: 1

sorry, not allowed to edit

Do you tried following steps?

1. go to SetupAssistant and check in "Get started" section all four check boxes

2. go to Project configurator : select you project and make it as Default

3. open window console (cmd promt) in directory "Lumberyard\1.16.0.0\dev" and type those commands:

3.1 - "lmbr_waf configure" - press enter

3.2 - "lmbr_waf build_win_x64_vs2015_profile -p game" - press enter

4. open your solution (Lumberyard\1.16.0.0\dev\Solutions) and swith from "[All] Profile" to [%yourProject%] Profile

5. select in solution tree project - Launchers::%yourProject%WindowsLauncher mouse right click and "Set up as StartUp project"

6. F7 (or select WAD in solution tree and build it)

7. see logs

....result is the same...

REMOVEDUPLOAD

I recently installed the latest version (15.9) of the Visual studio 2017 community. Is it related to this?

So a bit lengthier explanation of why the default args are a range, why removing the range and using 15.9.0 works here, and why this is the default range shipped with 1.16

The way Microsoft implemented their ranged version checks is different than the single version check. Ranged version checks check against the internal build number (ex. 15.9.xxxx where xxxx is the build number).

The single version check disregards the build number, so it will accept anything that reports its version as 15.9.0, regardless of build number.

So with that background, we decided to ship with this range because it reflects what our QA has fully tested. We used a build of 15.8.xxxxx, and the last known ABI incompatibility we had was moving from version 15.6 -> 15.7, so that is why it's the minimum of the range.

So yes, the correct answer here is to modify these however you see fit for your project's specific needs.

I'll make sure this feedback is taken into account for next release when we update the default version checks for 2017. We are trying to do our best to find a middle ground between letting customers know what we've actually tested for you, and where you may fall in to issues as Microsoft updates Visual Studio, which is how we've landed here. Thank you guys for your feedback :)

Thanks. Worked for me, saved me some serious pain.

Hi were you able to fix the issue eventually?

Oh now I understand. Glad that you fixed the issue, I run into the same one today. I just changed the code like you did. Now the project is being configurated. Fingers crossed.

Looks like it came from this website. It produces a familiar kind of software, which includes bulk SMS online sendings. You could write to them btw