Search Issue Tracker
Fixed in 2017.1.X
Votes
1
Found in
5.6.0f1
Issue ID
892185
Regression
No
[WASM] building with full exceptions fails
-e: see title, fails with build error
--works fine with just asm.js
-repro:
--create new project
--enable WASM and full exception support
--build for WebGL
--NOTICE it fails giving the following error:
Failed running "D:\Unity Installs\5.6.0f1\Editor\Data\PlaybackEngines\WebGLSupport\BuildTools\Emscripten_Win\python\2.7.5.3_64bit\python.exe" "D:\Unity Installs\5.6.0f1\Editor\Data\PlaybackEngines\WebGLSupport\BuildTools\Emscripten\emcc" @"D:\Work\Bugs\WASM_Except\Assets\..\Temp\emcc_arguments.resp"
stdout:
stderr:WARNING:root:--separate-asm works best when compiling to HTML. otherwise, you must yourself load the '.asm.js' file that is emitted separately, and must do so before loading the main '.js` file
warning: unresolved symbol: glGetInternalformativwarning: unresolved symbol: _ZN4FMOD13DSPConnection6setMixEfwarning: unresolved symbol: glUnmapBufferwarning: unresolved symbol: glMapBufferRangewarning: unresolved symbol: glFlushMappedBufferRangeTraceback (most recent call last):
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerLoop.SetPlayerLoop() function is ignored when playing game in Player
- Lighting data is carried over from one Scene to another when changing Scenes in the Play Mode
- The <sprite> tag inserted image from a Sprite Asset into the UI Builder Button disappears when the Inlined Style Text Shadow Horizontal or Vertical Offset is set to be more than 0 px
- Build fails when building with ILCPP Scripting Backend and ARMv7 as the Target Architecture
- Textures turn black in Player when they are referenced by a script instance
TaleOf4Gamers
Jan 13, 2018 11:31
Fixed - my fault, I was using the wrong syntax. I used:
function functionName () {}
instead of the suggested:
functionName: function () {}
Lesson: actually read the docs ;)
TaleOf4Gamers
Jan 13, 2018 11:27
Im using 2017.3 just FYI
TaleOf4Gamers
Jan 13, 2018 11:27
I just got this error.