> AFAIK, if you use the --embedded installation option you also need to call > emcc etc. with the --em-config option to tell the tools where the > .emscripten file is. > If you're just getting started with emscripten I would recommend not > installing with --embedded, this is only really useful if you need to > manage several emscripten installations in parallel on the same machine.
Good to know. However now I'm still using the .emscripten file in the $HOME. My main concern was the presence of an incompatible Clang on my system and the (non-working) emscripten 1.22 package I had installed (and then removed). Now I must set the $PATH variable (as described in the emsdk) manually and then I can still use .emscripten in my home folder. That's good for me (an official, working, system-wide, emsdk for Ubuntu would probably be better but I'm still happy this way). Thank you all for your answers (and to emscripten's developers that are putting such a big effort in this project!). -- 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]. For more options, visit https://groups.google.com/d/optout.
