-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Module.cwrap not finding symbols #849
Comments
(re-posting from right github account -- sorry. Now I can close!) Ok, so this can probably be reduced to a documentation bug. If you invoke emcc like so:
Then it does indeed work as advertised. I assume that something has changed in the behavior of either LLVM or Emscripten that causes this to be necessary now, whereas previously these functions were not stripped. Probably just updating the documentation on https://github.com/kripken/emscripten/wiki/Interacting-with-code to cite the EXPORTED_FUNCTIONS argument as mandatory for this kind of thing will suffice. |
This is probably LLVM doing more aggressive code elimination now. Thanks, i'll update the docs there about this. |
-s EXPORTED_FUNCTIONS switch does not definded. So, minified code was not able to run... emscripten-core/emscripten#849
When linking with `-o filename` (such as in various CMake build checks), the parameter passed to the linker is a temporary file, and it is passed as a bare filename (i.e. relative path without a `'/'`). In such cases, `outdir` would have been the empty string, and the final `tar` command would fail (actually the call to `subprocess.check_call(…)` is what fails).
Have been trying to get Module.cwrap to work. Followed the instructions on https://github.com/kripken/emscripten/wiki/Interacting-with-code -- I ran
Loaded that in Chrome, entered
into the Javascript Console and got this error:
The text was updated successfully, but these errors were encountered: