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
emmake fails and outputs thousands of libcxx errors #13017
Comments
Lol I ended up getting foobar challenge from Google while looking ways to fix this. Quite iconic moment. |
Something is probably wrong in your include paths. Try to build a hello world. And run with |
|
|
The This works fine under normal circumstances.. perhaps you have file called When I have problems like this I will sometimes at a |
There is a folder called ios in one of includes path. It has no relation to libcxx How come clang is that stupid to pick that up? |
I didn't think clang would pick up directories.. but I guess its possible. I imagine it should be looking for files only... perhaps this should be fixed in upstream clang? |
@sbc100 Seriously, it has to do with include paths somewhere. I was able to fix the error by manually including the paths by hands. I was using this macro before to automate the process,
In big projects, it would be painful to include them by hand. Nevertheless, you may investigate this case further if you want to. |
Re-opening this. I found an another error,
I export all, see my compiler flags,
|
Made a change and that fixed out the error
Any way to know which flags are link ones versus compile ones? |
Found it, https://github.com/emscripten-core/emscripten/blob/master/src/settings.js // In general it is best to pass the same arguments at both compile and link Better to add this to your official website docs |
Yes, those are useful. I think it would be even better if we could issue warning when they are used in the wrong situation. Like clang does "warning: argument unused during compilation". Also this only covers |
I'm on Windows.
I activate env vars by running
C:/Users/Administrator/emsdk/emsdk_env.bat
then I runemcmake .. && emmake make
and it started to print gazillions of errors related to libcxx and libcExample,
The text was updated successfully, but these errors were encountered: