Ah, that'll already solve my problem. Doesn't have to be pretty, just want
to be able to specify a specific version. Thank you so much!
On Wednesday, June 5, 2019 at 4:50:55 PM UTC-4, Gabriel CV wrote:
>
> It look like things have changed a bit recently.
>
> Actually, you can know the unique identifier of the last precompiled SDK
> available in the file "emscripten-releases-tags.txt" file (after issuing
> "emsdk update-tags" commands)
>
> On my side the contents is:
>
> {
> "latest": "1.38.33",
> "releases": {
> "1.38.33": "3b8cff670e9233a6623563add831647e8689a86b" // this is the
> unique identifier
> }
> }
>
> Then with that info I can do:
>
> ./emsdk install sdk-releases-upstream-<the_unique_identifier>-64bit
>
> This will install the 1.38.33. This is not very convenient I think, but it
> works
>
> Gabriel
>
>
> Le 05/06/2019 à 21:59, Patrik Weiskircher a écrit :
>
> Hey Alon!
>
> I have a question. We currently have our CI setup to compile specific
> versions that we define (currently we're running on `1.38.31`) using
> `emsdk install sdk-tag-${VERSION}-64bit`. We're currently running into a
> little problem after updating one of our dependencies and I figured I
> should just simply try out the latest version and hope it'll work. But it
> doesn't seem like we can do a `emsdk install sdk-tag-1.38.33-64bit` anymore
> - it says the version doesn't exist.
>
> Is this intended like this and from now on only `latest` is supported?
> This would be a little problematic for us as we really would like to pin
> down our versions (we previously had trouble with new versions introducing
> new bugs).
>
> Thanks for all your work, we all at PSPDFKit really appreciate it :)
> Patrik
>
> On Wednesday, May 29, 2019 at 1:45:45 PM UTC-4, Alon Zakai wrote:
>>
>> If you get emsdk master, and do
>>
>> emsdk install latest
>> emsdk activate latest
>>
>> then it will install 1.38.33 (or later, if there is one by the time you
>> read this) from the new emscripten-releases build infrastructure. We've
>> done some early testing recently as mentioned here:
>>
>>
>> https://groups.google.com/d/msg/emscripten-discuss/WhDtqVyW_Ak/8DfDnfk0BgAJ
>>
>> After fixing some issues, there seem to be no showstoppers, so this is us
>> moving to the next stage in the transition from the old builders to the new
>> ones. (If all goes well then the stage after this will be to remove those
>> old builders.)
>>
>> Please report any issues you see!
>>
>> Known issue: "no version information" warning on some linux machines,
>> https://github.com/emscripten-core/emscripten/issues/8697, that we need
>> to figure out.
>>
>> - 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 emscripten-discuss+unsubscr...@googlegroups.com <javascript:>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/emscripten-discuss/04241de6-3244-4c6f-b9ce-064d790815c6%40googlegroups.com
>
> <https://groups.google.com/d/msgid/emscripten-discuss/04241de6-3244-4c6f-b9ce-064d790815c6%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> 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 emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/emscripten-discuss/45a0a10c-35ce-4ac8-bb3f-8e9627bf0390%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
