I think this has merit for finetuning the builds of SDL2, zlib, libc and
libcxx, and supports what we discussed earlier about the ideal explicit
SDL2/ports build infrastructure. However, I think native optimizer at least
is in a different category, because building it depends on native compiler
available on the system. We need to be able to drive builds potentially
from Visual Studio 2010/2012/2013, Mingw-GCC, GCC and Clang. Given that
CMake already offers all of that and more (incremental building, IDE
integration and project dependency chaining), I think we should maintain a
CMake path for that at least. I authored a CMakeLists.txt for that now in
the pull request http://git.io/ZMqDkA . I hope it's not too much trouble to
maintain CMake config file side by side with the python native optimizer
build driver?

2014-12-18 17:33 GMT-05:00 Alon Zakai <[email protected]>:
>
> 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.

Reply via email to