EM_ASM not supported on MAIN or SIDE_MODULES #18199
Assignees
Comments
sbc100
added a commit
that referenced
this issue
Nov 16, 2022
This is a step towards supporting EM_ASM in side modules. See #18199
sbc100
added a commit
that referenced
this issue
Nov 16, 2022
This is a step towards supporting EM_ASM in side modules. See #18199
sbc100
added a commit
that referenced
this issue
Nov 16, 2022
This is a step towards supporting EM_ASM in side modules. See #18199
sbc100
added a commit
that referenced
this issue
Nov 17, 2022
This is a step towards supporting EM_ASM in side modules. See #18199
sbc100
added a commit
that referenced
this issue
Nov 17, 2022
This is a step towards supporting EM_ASM in side modules. See #18199
sbc100
added a commit
that referenced
this issue
Nov 17, 2022
The only way I could find to make work was to use `eval`. Sadly even using `new Function` didn't work since it evaluates the code not in the containing (module) scope but in the global scope. Fixes: #18199
sbc100
added a commit
that referenced
this issue
Nov 19, 2022
The only way I could find to make work was to use `eval`. Sadly even using `new Function` didn't work since it evaluates the code not in the containing (module) scope but in the global scope. Depends on WebAssembly/binaryen#5274 Fixes: #18199
sbc100
added a commit
that referenced
this issue
Nov 21, 2022
The only way I could find to make work was to use `eval`. Sadly even using `new Function` didn't work since it evaluates the code not in the containing (module) scope but in the global scope. Depends on WebAssembly/binaryen#5274 Fixes: #18199
sbc100
added a commit
that referenced
this issue
Nov 22, 2022
The only way I could find to make work was to use `eval`. Sadly even using `new Function` didn't work since it evaluates the code not in the containing (module) scope but in the global scope. Depends on WebAssembly/binaryen#5274 Fixes: #18199
sbc100
added a commit
that referenced
this issue
Nov 22, 2022
The only way I could find to make work was to use `eval`. Sadly even using `new Function` didn't work since it evaluates the code not in the containing (module) scope but in the global scope. Depends on WebAssembly/binaryen#5274 Fixes: #18199
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One of the very first blocker in Dynamic Linking is EM_ASM not supported on MAIN/SIDE MODULES.
em++: warning: EXPORTED_FUNCTIONS is not valid with LINKABLE set (normally due to SIDE_MODULE=1/MAIN_MODULE=1) since all functions are exported this mode. To export only a subset use SIDE_MODULE=2/MAIN_MODULE=2 [-Wunused-command-line-argument]
em++: warning: -sSIDE_MODULE + pthreads is experimental [-Wexperimental]
em++: warning: ignoring unsupported linker flag:
-soname[-Wlinkflags]em++: error: EM_ASM is not supported in side modules
ninja: build stopped: subcommand failed.
Warning: Command failed: set -o pipefail && cmake -DCMAKE_C_FLAGS="" -DCMAKE_CXX_FLAGS="" -GNinja -DCMAKE_TOOLCHAIN_FILE="/Users/suryaban/.venus_emscripten/upstream/emscripten/cmake/Modules/Platform/Emscripten.cmake" -DCMAKE_BUILD_TYPE=Debug -S app/proj/TritiumLib/linux_web/TritiumLib/ -B symbols/linux_web/Debug/TritiumLib && cd symbols/linux_web/Debug/TritiumLib && /opt/homebrew/bin/ninja && cd - 2>&1 | tee /Users/suryaban/Documents/Adobe_Git/tritium_dynamic_link/illustrator/tmp/compileBuildLogs/TritiumLib.txt
Use --force to continue
The text was updated successfully, but these errors were encountered: