On Tue, Dec 19, 2017 at 4:06 PM, Alon Zakai <[email protected]> wrote:
> Yeah, sorry about this. @juj handles the sdk builds, but he's been on > vacation and then traveling. I mentioned this to him so I hope he'll find > the time to fix it. > > In the meantime, I am told that on Mac there are more recent builds on > Brew. Or, you can build later tags or incoming from source using the emsdk > (but building LLVM+clang does take a while). > Great -- for now I'm building the tagged releases from source with the emsdk builder. (I'm maintaining parallel build environments on Mac and on Ubuntu under Windows 10's Linux subsystem. Can't use the native Windows build because I need full Unix build toolchain for the libraries I pull in.) Thanks for the offer to help - this is something we need to figure out how > to do better, and we do need help doing that. To think seriously about that > we need @juj, though (he's the only one that understands the current > setup), so that'll need to wait until he's back. > Just let me know when, we'll figure out how to improve it. :) I don't think I can host a Mac build box on Wikimedia infrastructure (we have many rules about free/open source!) but if I can help with the setup or provide a spare builder offline, I'd be happy to help. > Sort of separately from that, I've suggested that in addition to the > binary SDK we have an asm.js/wasm sdk, where the native parts are compiled > to asm.js or wasm. That would be easy to maintain, and would prevent people > from needing to build LLVM+clang when there isn't a native binary SDK. > However, it would be slower than a native build, obviously. Thoughts? > I love the idea -- this would require only node & python as a native prereq? That's got a great "dogfooding" character to it, and eliminates the complications of building binaries for Linux flavors that don't quite match up in low-level libraries... I worry a bit about performance though, particularly for the Unix autotools-style build chains that launch a lot of short compiler processes. Somewhat related -- has anybody done any work on making it easy to use emscripten in the build-time deps for an npm package? I've seen some clever hacks floating around for compiling individual C/C++ or Rust files and importing them as modules, but I'd love to be able to pull in a specific version of emscripten as a developer dependency, let npm download and install it in the dev modules tree, and build my asm.js/wasm code to feed into webpack etc... then when someone installs my module as a dependency, they've got the published precompiled code, but anyone checking out my module to recompile/modify it gets the right versions of everything. I'd rather install it locally than globally so versions are remembered and project-specific... But I also don't want to have to wait for emscripten to compile from source on 'npm install', so the npm builds would either need to carry multiple binaries or use the wasm-sdk trick. -- brion > On Tue, Dec 19, 2017 at 1:47 PM, Brion Vibber <[email protected]> wrote: > >> Precompiled binaries for emsdk-portable only seem to go up to 1.37.22 on >> Mac OS X, while a newer 1.37.25 tag is available for building from source. >> There also haven't been any precompiled nightly builds since 1.37.9 in >> March... >> >> Are Mac builds no longer being created on a regular basis? Is there >> anything we can do to help pitch in on maintaining a build bot? Thanks! >> >> -- brion >> >> -- >> 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]. >> 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 [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
