I'm testing with my cmake-based build setup and I'm having trouble with the new directory structure of the SDK.
I need to know the path to the emscripten installation in various places (among others, a cmake toolchain file), but as far as I can see, those files are now under a cryptic directory name: fastcomp/3b8cff670e9233a6623563add831647e8689a86b/emscripten/emcc Before it was something predictable like emscripten/incoming/emcc I don't want to "pollute" the global environment with environment or path variables (emcc is not in the path for instance), since I want to have different SDK versions side by side. Is there any chance we can have a standardized or "predictable" directory structure? Maybe a link to the actual SDK directory with a common name? Currently that's a bit of a show stopper for further testing since I would need to rethink my the entire emscripten integration into my build system. I'm also getting some errors during installation: Error downloading URL 'https://storage.googleapis.com/wasm-llvm/builds/osx/lkgr.json': HTTP Error 404: Not Found Error parsing lkgr.json! [Errno 2] No such file or directory: '/Users/floh/projects/fips-sdks/osx/emsdk-portable/upstream/lkgr.json' Cheers, -Floh. On Friday, 24 May 2019 02:45:05 UTC+2, Alon Zakai wrote: > > We have been working hard to replace the current build infrastructure with > a new system. The new one will be faster, have better support for testing, > and support the LLVM wasm backend (in fact this change is the last blocker > for us switching to that by default). As of now you can start to test this > out, if you do the following: > > * get latest emsdk master > * ./emsdk install latest-releases-fastcomp > * ./emsdk activate latest-releases-fastcomp > * optionally add the directory to the path with: source ./emsdk_env.sh > > That will install a new release tag, 1.38.33, from the new builders. > > Note that there is no change to "latest" (or other modes) - this just adds > this new "latest-releases-fastcomp". But after we are sure things work > well, the goal is to make "latest-releases-fastcomp" replace "latest". > > Please let us know if you see any issues with the emsdk or with using emcc > from that install! > > Notes: > > * You can replace "fastcomp" with "upstream" to use the LLVM wasm > backend. We'll have a larger announcement about this soon. > * The new builders don't download java yet, so closure compiler won't > work (unless you install it yourself). Aside from that, things should work > just like "latest". > > - Alon > > -- 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/fb29262a-bbad-4a29-b818-1d4ad861a5e1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
