search

aws / lumberyard

Amazon Lumberyard is a free AAA game engine deeply integrated with AWS and Twitch – with full source.
Other
2.04k stars 541 forks source link

Cannot create new project or build existing #442

Closed ExQDev closed 5 years ago

ExQDev commented 5 years ago

What is your question? I tried to build project, using VS2017, but it said that it cannot find QT, but I've installed all required modules via Setup Assistant, so I went to 3drparty/Qt/{ver}/ and found version just for msvc140, there were not Qt for msvc141(VS2017). I've found VS2015 iso and installed it, but now I get the next errors: Compilation failed - File: 'StreamSocketDriver.cpp.3470101.obj', Module: 'GridMate', Configuration: 'win_x64_vs2015|profile', error code 2 and other (this is the first one). How to fix it?

The full log is attached: lmbr_create.log

Which part of the engine are you asking about? Project Configurator

Which version of Lumberyard are you using? 1.21.2.0

joshbeacham commented 5 years ago

Please carefully confirm that you have met the installation requirements for visual studio as outlined here : https://docs.aws.amazon.com/lumberyard/latest/userguide/setting-up-system-requirements.html

Please confirm that you have your project selected as the default project in the Project Configurator. Instructions here : https://docs.aws.amazon.com/lumberyard/latest/userguide/configurator-projects.html#project-configurator-launch-projects

joshbeacham commented 5 years ago

You can use vs2017 if you want. The absence of a Qt folder for 2017 was not the cause of your issue. If you need help debugging 2017, please post a log for that issue.

ExQDev commented 5 years ago

My setup:

My installation: изображение изображение изображение изображение изображение изображение

My log for MSVS2017: lmbr_create.log

I think that exactly unexistence of vc141 version of Qt causes this problem. But even for VC140 and MSVS 2015 there are another errors, on top.

And for system requirements setup, I've installed and did everything shown in https://docs.aws.amazon.com/en_us/lumberyard/latest/userguide/setting-up-system-requirements.html .

The default project is set: изображение

joshbeacham commented 5 years ago

ExQDev, thank you for this detailed information.

Concerning your VS2015 and VS2017 log - The command you are running "build_win_x64_vs2015_profile --enabled-game-projects=def -p def" doesn't match the screenshot from the project configurator. I don't see any project named "def" in that screenshot. Can you explain why you included "--enabled-game-projects=def" in your build command? You should select the project that you want to build as the default in the Project Configurator, and omit the "--enabled-game-projects" option. Also, the "-p" option is for the build spec, not for the project. I suggest using "-p all". See the WAF build documentation here https://docs.aws.amazon.com/lumberyard/latest/userguide/waf-commands.html

Concerning the VS 2017 log - I believe that you are using a version of Visual Studio that is outside of the officially supported versions. To resolve this issue, you can expand the range of Visual Studio versions that WAF looks for. To do so, please open the file \dev_WAF_\user_settings.options, scroll to the bottom and replace the line for win_vs2017_vswhere_args with win_vs2017_vswhere_args = -version [15,16) Be sure to remove the leading semicolon on that line. Rebuild, and let me know if that solves your issue.

ExQDev commented 5 years ago

@joshbeacham There's no 'def' project on screenshot, because I'm trying to create it and it fails. When it fails it destroys the new project. When I'm using "-p all" the result is the same.

I already tried to change versions between 14,15 and 16. The results with 15 and 16 are the same.

joshbeacham commented 5 years ago

Per your concern about Qt, see the following screenshot from my working vs2017 installation. image

Please confirm that you've updated win_vs2017_vswhere_args as provided, then run "lmbr_waf build_win_x64_vs2017_profile -p all" from a command prompt and provide the resulting log. Thank you.

Thank you for previously reviewing the installation requirements and confirming your information is correct. If the the change to win_vs2017_vswhere_args (making sure to remove the semicolon) does not work, you could try try aligning your installation to the below screenshots see if this might address the issue? image image

ExQDev commented 5 years ago

@joshbeacham The build log: build_err.log Thank you for your screens, I've found that I've not installed MFC and 2015.3 toolset v140. I will install them and check it again.

ExQDev commented 5 years ago

@joshbeacham after installing these components there are no changes in build log. Here're screens: изображение изображение изображение изображение

ExQDev commented 5 years ago

Here's configure log: https://pastebin.com/6iy8SJD4

Installer sees the MSVS2017, but configurer not: изображение

joshbeacham commented 5 years ago

This makes me think that the build can't find Qt because the configure is failing. The configure log suggests that WAF cannot find your VS install, which is what I originally suspected. Would you please upload your \dev\WAF\\usersettings.options file? Have you made any changes to any other file in the \dev\_WAF\\ directory?

ExQDev commented 5 years ago

No, I didn't. This file is auto-configured. Github do not allow to upload that file type, I'll rename it. user_settings.txt

joshbeacham commented 5 years ago

I'm wondering why you did not follow the explicit instructions I provided two separate times to modify that file?

Concerning the VS 2017 log - I believe that you are using a version of Visual Studio that is outside of the officially supported versions. To resolve this issue, you can expand the range of Visual Studio versions that WAF looks for. To do so, please open the file \devWAF\user_settings.options, scroll to the bottom and replace the line for win_vs2017_vswhere_args with win_vs2017_vswhere_args = -version [15,16) Be sure to remove the leading semicolon on that line. Rebuild, and let me know if that solves your issue.

Please confirm that you've updated win_vs2017_vswhere_args as provided, then run "lmbr_waf build_win_x64_vs2017_profile -p all" from a command prompt and provide the resulting log. Thank you. Thank you for previously reviewing the installation requirements and confirming your information is correct. If the the change to win_vs2017_vswhere_args (making sure to remove the semicolon) does not work, you could try try aligning your installation to the below screenshots see if this might address the issue?

Please modify that file as requested, and then run a configure and build, and share the logs.

ExQDev commented 5 years ago

@joshbeacham

win_vs2017_vswhere_args = -version [15,16) *Square closing bracket

Thank you very much, I've been inattentive and modified another line of version, so had no success. Now it is fixed. The end of log is

gins\UiCanvasEditor.dll Bin64vc141\EditorPlugins\UiCanvasEditor.pdb Bin64vc141\EditorPlugins\UiCanvasEditor.dll.manifest
   Creating library e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\Editor.lib and object e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\Editor.exp
   Creating library e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\EditorPlugins\EditorModularBehaviorTree.lib and object e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\EditorPlugins\EditorModularBehaviorTree.exp
   Creating library e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\EditorPlugins\EditorAssetImporter.lib and object e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\EditorPlugins\EditorAssetImporter.exp
   Creating library e:\\Amazon\\Lumberyard\\1.21.2.0\\dev\\Bin64vc141\\EditorPlugins\\CryDesigner.lib and object e:\\Amazon\\Lumberyard\\1.21.2.0\\dev\\Bin64vc141\\EditorPlugins\\CryDesigner.exp
   Creating library e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\Gem.Water.Editor.c5083fcf89b24ab68fb0611c01a07b1d.v0.1.0.lib and object e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\Gem.Water.Editor.c5083fcf89b24ab68fb0611c01a07b1d.v0.1.0.exp
   Creating library e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\EditorPlugins\DeploymentTool.lib and object e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\EditorPlugins\DeploymentTool.exp
   Creating library e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\EditorPlugins\ProjectSettingsTool.lib and object e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\EditorPlugins\ProjectSettingsTool.exp
   Creating library e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\Gem.SurfaceData.Editor.5de82d29d6094bfe97c1a4d35fcd5fbe.v0.1.0.lib and object e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\Gem.SurfaceData.Editor.5de82d29d6094bfe97c1a4d35fcd5fbe.v0.1.0.exp
   Creating library e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\Gem.Camera.Editor.f910686b6725452fbfc4671f95f733c6.v0.1.0.lib and object e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\Gem.Camera.Editor.f910686b6725452fbfc4671f95f733c6.v0.1.0.exp
   Creating library e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\EditorPlugins\ComponentEntityEditorPlugin.lib and object e:\Amazon\Lumberyard\1.21.2.0\dev\Bin64vc141\EditorPlugins\ComponentEntityEditorPlugin.exp
   Creating library e:\\Amazon\\Lumberyard\\1.21.2.0\\dev\\Bin64vc141\\EditorPlugins\\UiCanvasEditor.lib and object e:\\Amazon\\Lumberyard\\1.21.2.0\\dev\\Bin64vc141\\EditorPlugins\\UiCanvasEditor.exp
[WAF] 'build_win_x64_vs2017_profile' finished successfully (1h24m57.736s)
[WAF] Executing 'package_win_x64_vs2017_profile'
[WAF] 'package_win_x64_vs2017_profile' finished successfully (13.892s)
[WAF] Executing 'deploy_win_x64_vs2017_profile'
[WAF] 'deploy_win_x64_vs2017_profile' finished successfully (2.171s)

Maybe it is worth to make "How to install/build" doc with step-by-step instructions? For so stupid as me and another people who get no success on first build)

At the last, should I remove VS 2015 or it is necessary? And it would be better, to add VS2019 support, MS are so persistent with updates..

joshbeacham commented 5 years ago

You are welcome. I am glad your issue is resolved.

Regarding VS2015 - You can remove VS2015, it is not necessary.

Unfortunately, this is an issue for almost everyone that installs the engine, because the Lumberyard team decided to hard code their supported VS versions into the configuration files in a way that causes build failures that emit nebulous and cryptic errors messages that appear to point to entirely unrelated causes. This issue would be eliminated if they would ship Lumberyard with a broader range of accepted VS versions and instead issue a warning in the log if the VS version found is outside of the supported range.

If you would like to offer suggestions or feedback to the lumberyard team, you can contact them via email or the forums, details provided here https://docs.aws.amazon.com/lumberyard/latest/userguide/lumberyard-blog-forums-feedback.html

You are also welcome to join the Lumberyard Community Discord server here https://discord.gg/GqbPQqT

ExQDev commented 5 years ago

Thank you very much again, I have just joined Discord server, and I will check thier feedback! Now I will close thread as resolved.