-
Notifications
You must be signed in to change notification settings - Fork 442
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty EmscriptenApplication Crashed #376
Comments
Hmm, this seems to be the culprit. Maybe caused by a newer emscripten version... Try enabling assertions, maybe you'll get more info: target_link_options(MyApplication PRIVATE
# Set debugging flags (assertions and demangle)
$<$<CONFIG:DEBUG>:-s ASSERTIONS=1 -s DEMANGLE_SUPPORT=1>) |
Looking at Emscripten's issues, especially emscripten-core/emscripten#9397, it seems like this |
I have to admit the new Emscripten versions don't work for me very well (complaining about Clang version mismatch and whatnot), so I'm personally at 1.38.38 (and I'll look at this before release, but so far it seems it's one of those "emscripten is broken" days ... let's wait until things settle down there :D |
Have tested with emsdk 1.38.30 and 1.38.46, both with error:
|
@linuxaged did you get any further with this? I wasn't able to reproduce on my side. Keeping this open until we figure it out, but since it seems to be that Emscripten is to blame I don't think it's blocking the 2019.10 release. |
update
|
Nice. The |
by the way, cmake toochain files not included in the bootstrap Emscripten project archive, complete project maybe more friendly to newcomers : > |
It's a Git submodule and the ZIPs created automagically by github don't include these :/ Not sure how to fix that (besides manually putting all files there..). |
Anything left to be done here? :) |
fine to close |
follow the official emscripten example, app crashed:
console log:
emsdk version:
app build log:
http server log:
The text was updated successfully, but these errors were encountered: