> > >> 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. > > No output, it happens during cmake's compiler / compile feature detection. Maybe cmake is supressing console output on purpose there to not spam the console with errors that might be expected during the detection.
> 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? > > It's not a particularly slow laptop, I have set it up for Win10 / Ubuntu dual boot, and the same process on Linux is about the same as on my Mac laptop (which is acceptable). I think it's a Windows issue, IME clang on Windows is a lot slower than on OSX or Linux for some reason. Maybe the Windows build is accidentally using a debug build of LLVM, I didn't pay attention to this, and it was downloading a prebuilt package, so that would be hard to notice anyway. Cheers, -Floh. -- 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/56218175-49c2-4199-a291-39296350452a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
