I've successfully used it and it works alright for me. More in a general sense, I wonder whether this could be a part of a wider approach to "cleanly" set up the emscripten tool chain. I know that the SDK exists, but it doesn't make sure of all external dependencies (node, python, ...), including header files and native compiler toolchains which are sometimes needed by hand-coded configure scripts. In fact, I am presently setting up my Emscripten-based toolchain with Docker and wonder if (and how) this could be generalized...
On Friday, December 19, 2014 8:33:20 AM UTC+10, Alon Zakai wrote: > > I pushed to incoming a "system builder" tool, embuilder.py It lets you > manually ask that things be built, like libc, the native optimizer, zlib > from ports, etc. > > embuilder.py -help shows the available operations. > > This addresses part of the requests for a more manual way to build things > from emscripten ports. It also allows other manual building, which I have > heard some projects have been doing, of things like libc, etc. > > For example, you might do this: > > ./embuilder.py build zlib > ./emcc code.cpp -s USE_ZLIB=1 > > and the first command will already ensure that zlib is fetched and built. > > Thoughts? > > - 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
