- Le plus récent
- Le plus de votes
- La plupart des commentaires
It looks like your project is configured to build using VS2019 but VS2019 is disabled in Setup Assistant perhaps?
Which version of Visual Studio are you using?
Here's some help if the issue is your VS version:
Run Setup Assistant and verify you have the correct version(s) of Visual Studio checked on the bottom of the Get Started page.
Verify you have correctly installed the version of Visual Studio and its prerequisites. You can find more info here:
https://docs.aws.amazon.com/lumberyard/latest/welcomeguide/wg-requirements.html
Now reconfigure your project. We'll do this at the command line. First, ensure you have the correct default project set in Project Configurator, and that you have all the Gems you need enabled. Make sure to save the configuration.
Now open a command line and navigate to the dev directory of your Lumberyard installation.
cd D:\Amazon\Lumberyard\1.25.0.0\dev\
Run the configure command. This command will generate your solutions and may take few minutes.
lmbr_waf configure
Now run the build command for the version of Visual Studio you are using. One of the following:
lmbr_waf build_win_x64_vs2017_profile -p all --progress or lmbr_waf build_win_x64_vs2019_profile -p all --progress
the build process can take some time, possibly a couple of hours depending on your machine and what components need to be built.
There is a warning there saying it can't find a valid WIndows SDK. That's a requirement.
From the link I posted above, double check you Visual Studio Installation and make sure you have installed all the required features for Visual Studio particularly Step 4 in Prerequisites.
https://docs.aws.amazon.com/lumberyard/latest/welcomeguide/wg-requirements.html
Make sure you have completed all the steps on this page and run configure and build again.
If it still won't build, we'll dig into your logs and figure this out.
I've done it, but there is another problem:
REMOVEDUPLOAD
It has not completed yet.
So i had the same issue with the project configuration. So I just ran the waf build system by the command line. The command that I ran was 'lmbr_waf build_win_x64_vs2019_profile -p all -progress" Note: That if you don't have VS2019 selected then replace the 'vs2019' with 'vs2017'. You can replace 'all"(which builds engine, project, editor, and tools) command with 'game_and_engine'(which only builds the engine and game project.
Source: WAF commands running lmbr_waf -help
@REDACTEDUSER
Hope it finished OK.
The initial build time is lengthy and a known issue the team is working to address. It can take over 2 hours on a modern CPU. Subsequent builds for minor changes and adding additional gems should be much quicker.
Cette publication est fermée : l'ajout de nouvelles réponses, commentaires et votes est désactivé.
Contenus pertinents
- demandé il y a 2 mois
- Réponse acceptéedemandé il y a un an
- demandé il y a un an
- demandé il y a 7 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- Comment dépanner mon environnement Amazon MWAA bloqué à l'état « Creating (En cours de création) » ?AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an