You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, me again. :-) I'm trying to use this as a basis for the asmdom::direct example that we discussed (since the instructions are so clear here). I got up to the npm start instruction, and it is failing with this error:
$ npm start
> asm-dom-boilerplate@0.1.0 start /home/tmadden/local-dev/asm-dom-boilerplate
> make start
emcc \
-O3 -Wall -Werror -Wall -Wno-deprecated -Wno-parentheses -Wno-format \
--bind \
-include node_modules/asm-dom/cpp/asm-dom.hpp \
temp/o/index.o \
node_modules/asm-dom/cpp/asm-dom.cpp \
-o temp/app.bc
emcc: error: Assuming object file output in the absence of `-c`, based on output filename. Add with `-c` or `-r` to avoid this warning [-Wemcc] [-Werror]
I'm not that familiar with .bc files, but it seems maybe recent versions of Emscripten behave differently than what this was developed against? I'm using Emscripten 1.40.1.
I tried adding -c, but then it just gave a different error, and it seems like that's probably not the right direction, so I decided it was time to consult the expert. ;-)
The text was updated successfully, but these errors were encountered:
it seems like you need to use emcc -c to generate object files (remove -o). emcc -c will automatically generate an object file with it's own naming convention. So you need to also change $(BC) to be asm-dom.o. However, I'm running into other issues.
Hi, me again. :-) I'm trying to use this as a basis for the asmdom::direct example that we discussed (since the instructions are so clear here). I got up to the
npm start
instruction, and it is failing with this error:I'm not that familiar with
.bc
files, but it seems maybe recent versions of Emscripten behave differently than what this was developed against? I'm using Emscripten 1.40.1.I tried adding
-c
, but then it just gave a different error, and it seems like that's probably not the right direction, so I decided it was time to consult the expert. ;-)The text was updated successfully, but these errors were encountered: