Skip to content
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

Build failing #12

Open
tmadden opened this issue Jan 25, 2021 · 2 comments
Open

Build failing #12

tmadden opened this issue Jan 25, 2021 · 2 comments

Comments

@tmadden
Copy link

tmadden commented Jan 25, 2021

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. ;-)

@yihan0512
Copy link
Contributor

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.

@mbasso
Copy link
Owner

mbasso commented Jul 8, 2021

Hi,
sorry for the very late reply.
@yihan0512 , thanks for your PR!
The issue should be fixed now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants