On Thu, May 30, 2019 at 4:37 AM Floh <flo...@gmail.com> wrote: > It's "mostly" working fine here (tested with "latest"): > > - Linux and OSX work out of the box (maybe because I have "accidentally" > Java installed. > - on Windows running the Closure pass fails because of missing Java > > Will Java be provided by emsdk or do I need to care of that myself? > > Thanks, it looks like we used to bundle java on windows, but nowhere else. I opened
https://github.com/emscripten-core/emsdk/pull/253 to match that behavior on the new builds. > And some "nice-to-have" feedback: > > - Is it already time to write tickets for the latest-releases-upstream > version? Compilation with my code appears to work, but I'm getting runtime > errors for EM_JS functions: > > failed to asynchronously prepare wasm: LinkError: > WebAssembly.instantiate(): Import #61 module="env" > function="_sapp_js_create_textfield" error: function import requires a > callable > clear-sapp.html:39 LinkError: WebAssembly.instantiate(): Import #61 > module="env" function="_sapp_js_create_textfield" error: function import > requires a callable > > Definitely file bugs on upstream if you find any! Yes, please file this one with a testcase, it doesn't look like a known issue. - The very first emcc invocation after another SDK version is > installed/activated (in my case during the cmake compiler detection) takes > *very* long on Windows, something like 5..10 minutes, and without feedback, > so it appears like the build process hangs. Under the hood there's some > compilation happening (maybe binaryen?). The time this takes is so > "uncomfortably long" that I would consider it a bug. May be in the future > it would make sense to also provide precompiled artifacts for those hidden > compilations for the "prebuilt" SDK versions? > Did it not say what it was doing during that pause? Like it should say if it was building binaryen, or system libraries, etc. It should print that even without EMCC_DEBUG=1 in the env, but that may provide even more info. We do provide binaryen pre-built, but not system libraries (but we plan to). If it's building binaryen from source, thats a bug. (I don't think we even download the binaryen sources, though.) 5-10 minutes sounds extremely long for either binaryen or system libraries, though. Was that on a slow machine? If not, then that sounds bad. Perhaps python doesn't detect how many cores there are and the builds are single-core, or maybe somehow our build of LLVM is debug and not release, or something like that? - Alon > > Cheers, > -Floh. > > On Wednesday, 29 May 2019 19:45:45 UTC+2, 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/emscripten-discuss/3ee49945-abce-4a0e-8814-69e38a1f1d49%40googlegroups.com > <https://groups.google.com/d/msgid/emscripten-discuss/3ee49945-abce-4a0e-8814-69e38a1f1d49%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/CAEX4NpQA_G%2BCY69FujJ6W4fgY3ANNrOrQu1A5Q8vWzR0PWf0zQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
