Replies: 2 comments 2 replies
-
Hmm, I'd expect that to just work since include paths you include should have precedence over system ones... so that is odd. Somehow your SDL2 build ends up including headers from SDL1 in the sysroot. Perhaps @sbc100 has an idea? Otherwise, maybe seeing the verbose output of emcc/clang ( In general, you can clear the sysroot cache ( |
Beta Was this translation helpful? Give feedback.
-
It does! I've stuck a fix in the build script here for now: libsdl-org/SDL@51be30f Thanks! |
Beta Was this translation helpful? Give feedback.
-
(This felt like it shouldn't be a bug report, but let me know if it should be instead!)
This is with 3.1.18 (just a fresh emsdk clone and
emsdk install latest
from today).I'm trying to build SDL from source, but Emscripten is supplying its own copy of SDL in
emsdk/upstream/emscripten/cache/sysroot, which is causing me issues like this, where it is favoring the sysroot headers over the ones included with the project while building the project:
This isn't an issue on our GitHub Actions builds, because we're building with a significantly older emsdk at the moment, but this will eventually cause up problems when we upgrade.
Is there some way to disable the cache, either entirely or just parts of it, temporarily or permanently?
Thanks!
--ryan.
Beta Was this translation helpful? Give feedback.
All reactions