Ok, great news, I also removed the --em-config arg now (in addition to the --cache arg) and it works perfectly, this simplifies my cmake toolchain setup a lot. I'm passing in the absolute path to the directory where the emcc etc... tools are located, and in the cmake toolchain file set the compiler variables to absolute paths (so "/abs/path/to/emscripten/emcc").
No environment variables or additions to the PATH variables needed, only the absolute paths to the toolchain tools. It's perfect now :) -Floh. On Thursday, 21 May 2020 18:41:02 UTC+2, Floh wrote: > > > I really want to stop people from trying to do this. I'd much rather > the PATH was way one finds emscripten. e.g. `which emcc`. Failing that > an environment variable. > > What about having several emsdk installations side by side though, without > any of them being the "default version". > > But if I understand your other posts right, that won't be an issue in the > future (e.g. if all the tools in the SDK can figure out the location of > "their" SDK without external hints like the --em-config or --cache command > line args). Ideally this should work without having the PATH or setting > "global" environment variables. > > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/0f5d7a6c-83bc-437f-9f3d-b9ae5a940df9%40googlegroups.com.
