Emscripten SDK 1.29.0 (higher version) not supported

anonymous_user_2ec798d9 · February 15, 2015, 3:44pm

I have installed Emscripten SDK as the HTML5 start up doc said. but know when i try to run GenerateProjectFiles.bat, this is what I see:

although it is strange to see a higher version is not compatible, I am thinking of changing the active version. anybody knows how to do that?

P.S. Environment Variable is set properly

JoJo_2nd_1 · February 15, 2015, 4:01pm

Change ExpectedSDKVersion in UEBuildHTML5.cs to the version you want. Then regenerate projects. FWIW we are using 1.29.0 so you shouldn’t have any issues using it.
This behaviour will change in the future (4.7 release I think) to allow later SDK version to work without this change.

anonymous_user_2ec798d9 · February 16, 2015, 7:49am

Thnx. It is great to have responses this fast from staff.

HaxO · December 13, 2016, 7:48pm

What version are you using now? I am getting a ton of errors with 1.35.0, 1.29.0, 1.12.0

Here is the log.

Edit: Tried new versions.

[link text][1]

118532-frontendbuild_errors25.log (5.04 KB)

anonymous_user_a08c0bf2 · December 20, 2016, 10:27pm

Emscripten is set up by default if you’re in a newer version of the engine. If you are still having trouble, please post a new thread to AnswerHub with additional details.

Thank you!

anonymous_user_f0fea7ad · March 9, 2017, 2:07pm

In the future (possibly when UE 4.16 ships), UE4 will be using something closer to Emscripten SDK 1.37.3 which has WebAssembly support, and there will be support for people to use a global system environment variable EMSDK to point to a custom location of their own installed Emscripten, if they want to try to use another version for development purposes or bug testing.

The version of Emscripten that UE4 ships with is expected to be somewhat static, i.e. users will not change the internal Emscripten version that is used, but attempting to use a different version will likely be done via pointing to a custom EMSDK. (This is a divergence from older ~UE4.10 era where the UI did have fields to point to Emscripten SDK locations, that turned out to be a bit messy)