Well, the issue there is that we would need to refactor libc++ into modules, or something like that? Or add ifdefing to libc++. Unless there is a better way that I can't think of.
The system builder tool just offers a way to ask for a system component to be built, it currently can't do anything the system couldn't already do. But, if we find a way to modularize libc++, then an option for the system builder would indeed be the right place to put it. - Alon On Fri, Dec 19, 2014 at 1:25 PM, Floh <[email protected]> wrote: > > Will this allow is to build libc++ without iostream constructors as > discussed earlier? (https://github.com/kripken/emscripten/issues/2785) > > Cheers, > -Floh. > > Am Donnerstag, 18. Dezember 2014 23:33:20 UTC+1 schrieb Alon Zakai: > >> 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. > -- 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.
