Unable to build CryEngine 5.3.3 sources

#1
I am trying to build the CryEngine sources from git (https://github.com/CRYTEK/CRYENGINE) but it always fails with the following error:

Code: Select all

Build failed -> task in 'mono (win_x64|release)' failed (exit status 1): {task 74193392: mono CrySystem.cs,CryMonoBridge.cs,CryAISystem.cs,CryNetwork.cs,CryInput.cs,ForwardDeclarations.cs,CryAudio.cs,CryDynamicResponseSystem.cs,CryCommon.cs,CryPhysics.cs,CryMovie.cs,CryLobby.cs,CryFont.cs,CryLiveCreate.cs,CryScriptSystem.cs,CryAnimation.cs,CryEntitySystem.cs,Cry3DEngine.cs,CryGame.cs,CryRender.cs,CryAction.cs -> CryEngine.Common.dll} '' Please Press Any Key to Continue
How can I fix this?

Re: Unable to build CryEngine 5.3.3 sources

#3
- clone the release branch from git
- execute cry_waf.exe to download SDKs
- enter build command to console

No matter what configuration (release, profile, gamezero, gamesdk) all builds fail with the same error shown above. Compiler is --project-spec so I guess it uses the one from Visual Studio 2015 that I have installed. Any suggestions?

Re: Unable to build CryEngine 5.3.3 sources

#8
- clone the release branch from git
- execute cry_waf.exe to download SDKs
- enter build command to console
is so wrong.


you need latest python and cmake
download source and sdks
https://github.com/CRYTEK/CRYENGINE/releases
extract sdks to code/sdks folder(see snapshot)
execute cry_waf

and meet the requirements
http://docs.cryengine.com/display/CEPRO ... d+Versions
Thanks, I'll give that a try and report later.

Re: Unable to build CryEngine 5.3.3 sources

#9
Still doesn't work. I made sure that I had the newest versions of cmake (3.9.0-rc6) and python (3.6.2) installed. Then I downloaded the Cryengine sources (5.3.4) from release branch and the SDKs (5.3.3) and extracted them to Cryengine/Code/SDKs. Then I started cry_waf.exe which did not download the SDKs because they were already there. But still I get the same error when I try to build. As far as I can see I match the requirements from your link, too. I recently installed Visual Studio Community 2015 and Windows SDK.

As it seems to work for other people, so the problem seems to be somewhere at my setup. Is there anything I don't see?

Who is online

Users browsing this forum: No registered users and 1 guest