If I leave the folder structure intact, it seems to work. But if I try to reproduce the folder structure found in the Windows installer, the activation fails to find Clang and Emscripten.
Right now I have to leave the Clang folder like this: ...\clang\tag-e1.36.1\build_tag-e1.36.1_vs2013_64\Release\bin\<clang binaries> If I try to set it like the Windows installer, like this: ...\clang\e1.36.1\<clang binaries> Its never found. How is this handled in Emscripten activation script? Thanks! On Monday, March 14, 2016 at 2:26:34 PM UTC-4, Alon Zakai wrote: > > You need the emscripten source tree, except for tests/. And the binaries > of LLVM+clang (that the LLVM build produces in a bin/ folder). > > Perhaps the SDK already has a way to do that, I'm not sure, or it might be > nice to add it. > > On Mon, Mar 14, 2016 at 7:24 AM, Robert Goulet <[email protected] > <javascript:>> wrote: > >> Hi all, >> >> After I've run an Emscripten build successfully (i.e. emsdk install >> --build=Release sdk-tag-1.36.0-64bit), which files can I delete that are >> no longer necessary, and still preserve the integrity of Emscripten? What's >> the clean way to distribute Emscripten without source files and/or >> temporary build files? Is there any procedure to follow, or documentation >> on the topic? >> >> Thanks! >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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.
