Thanks for the reply! I would prefer to call emsdk with an option to query
the current path instead of symlinks (not sure how it works now, but
symlinks and Windows command line tools and/or python on Windows was always
a bit wonky).
Since I don't have a single global emscripten SDK installation, but instead
several local installations side by side it would be important for me to
get a relative path component (like in your example). Basically it would be
fine if this works:
> emsdk path sdk-latest-64bit
In that case the path would be relative to the emsdk script, which imho
makes the most sense? The really critical part is the "1.37.9" though.
Am Mittwoch, 19. April 2017 16:17:08 UTC+2 schrieb jj:
> Currently there does exist a meta-target
> ./emsdk install sdk-latest-64bit
> to install the latest 64-bit precompiled SDK, but that does not use a
> fixed directory. Could do a emsdk/emscripten/stable directory, although I
> wonder if it might be better to use symlinks for this instead? Another way
> could be to have a "emsdk path <toolchain>" command, which would output the
> directory where the given toolchain is installed to, i.e, "emsdk path
> emscripten-latest-64bit" would spit out "emsdk/emscripten/1.37.9/". One
> could then also ask for an active toolchain, i.e. "emsdk path emcc", which
> could spit out whatever is activated to emsdk. Custom CMake tools could do
> a configure time process invocation to query these. Would that make any
>> PS: one minor wish I'd have is to have a meta-version-tag for the latest
>> precompiled stable version, or does this already exists and I'm not seeing
>> I'd basically like to do:
>> ./emsdk install sdk-stable-64bit
>> And I would (currently) get the precompiled sdk-1.37.9-64bit version (or
>> whatever the latest precompiled version is), but under the path
>> "emsdk-portable/emscripten/stable", and not
>> "emsdk-portable/emscripten/1.37.9" (similar to how "incoming" works).
>> This would simplify automated build environment setup a lot (for instance
>> cmake toolchains which need to find the path to the SDK).
>> Am Dienstag, 28. März 2017 09:37:05 UTC+2 schrieb Floh:
>>> I had to do a little emergency fix yesterday on my build wrapper scripts
>>> and cmake toolchain files because the SDK root path seems to have changed
>>> from emsdk_portable to emsdk-portable, but other then that little hickup it
>>> looks good so far (testing on OSX, Linux and Windows).
>>> So far I'm testing the incoming version, I'll try to test the
>>> precompiled Linux version next as this would save us time when setting up
>>> new build servers.
>>> Cheers (and thanks for providing a precompiled Linux toolchain!),
>>> Am Montag, 27. März 2017 21:31:48 UTC+2 schrieb jj:
>>>> Hi all,
>>>> we have now completed a switch in the release management infrastructure
>>>> to automate the compilation and packaging of new compiler versions as soon
>>>> as they are tagged and become available. Please help give this a try on
>>>> this works!
>>>> To get to the new autocompiled builds, simply run "emsdk update" in
>>>> your existing Emscripten installation, and then run "emsdk update-tags" to
>>>> verify that the up to date latest list of tags has been obtained. You
>>>> should start seeing precompiled Emscripten 1.37.9 tags and earlier, as the
>>>> build bots finish packaging and uploading them.
>>>> If you bootstrap to Emscripten SDK via git, then use "git pull" instead
>>>> of "emsdk update" to get to the latest version.
>>>> A new feature is that we now also have precompiled compiler toolchains
>>>> for 64-bit Linux as well, which was earlier strictly compiled from source.
>>>> The builds are done on an Ubuntu 16.04 system, and I'm not quite sure how
>>>> these will work on other Linux distros, so curious to hear experiences
>>>> One of the changes here is that we are dropping the Windows specific
>>>> NSIS installers, and on Windows, Emsdk is also offered as a "portable"
>>>> package, i.e. just download and unzip.
>>>> Fresh downloads are available at:
>>>> - Windows:
>>>> - Linux and OS X:
>>>> Check out the README at
>> 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
>> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.