-
Notifications
You must be signed in to change notification settings - Fork 200
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
Ninja config fails to generate a wasm build on Windows #283
Comments
argh, that looks familiar... see here: floooh/fips#163, I was sure I had fixed that in this commit: floooh/fips@240c3b9, but seems it isn't working everywhere, could be that the previous version worked with ninja, but not make, and the fix makes it work with make, but broke ninja :/ If it works with make I would recommend this as a workaround. With ninja you will sooner or later run into cmdline length issues on Windows. With make this is fixed by using linker-response-files. |
...hmm but that other ticket also uses ninja, not sure what's happening there, I currently don't have a machine with emscripten installed (installing now, but can only check tomorrow evening). |
Thank you for your response! It is not super urgent, so please take your time :) In a meantime, I will try to look at this too. |
Hmm I cannot reproduce this on a Windows7 machine both with the normal terminal or Cmder...
works... maybe it's the python or cmake version? I have:
|
Indeed in new versions of Oryol and Fips the problem is gone! Sorry for hanging issue. |
Hi, I have a little trouble with the combination of Ninja builder and wasm generator on windows (wasm-ninja-release).
It goes fine until the linking and then the error looks like:
Ninja works fine with the asm.js build.
Make works fine with any build (but is not available by default on Win).
The text was updated successfully, but these errors were encountered: