Currently ./emsdk --list does that. It shows INSTALLED if the tool is installed in emsdk, a star * if the given tool is installed and also set up to be currently used in ~/.emscripten, and set up in PATH. If the tool is activated to ~/.emscripten, but not in current PATH, the star will me marked in parentheses (*).
Perhaps we should extend that list to include 3rd party tools that emsdk doesn't install by itself on the given OS? 2014-12-29 19:34 GMT+02:00 Floh <[email protected]>: > I think a 'diagnose' script/command would be nice which checks if required > tools are in the path and have at least the right versions, and outputs a > 'toolname: found' or '...: NOT FOUND' on the console. > > This could be called with './emsdk check' or './emsdk diag', and could be > called by default after installing or updating. In my fips build system > python script I call python's subprocess.check_output with 'toolname > --version' and look at the version string. > > Am Montag, 29. Dezember 2014 15:36:07 UTC+1 schrieb jj: >> >> The Emscripten SDK sets up all the external dependencies only on Windows, >> because that is the only environment where bootstrapping is not readily >> available and where it is technically feasible to do so without disrupting >> the user's system. For Linux and OSX there is no such thing to my >> knowledge, because the way to set up the dependencies vary by OS version >> and by person's preferences. If someone has interest in helping to set >> something up for Linux and OSX side and has an idea how to do it so that >> it's more worth than trouble across the variety of user environments out >> there, I'd be very happy to discuss. As an alternative, perhaps some kind >> of checking script which attempts to use all the required dependencies, and >> if not met, aborts and issues instructions on how the user might be able to >> install those to his system to continue, might be enough? >> >> 2014-12-27 7:12 GMT+02:00 Soeren Balko <[email protected]>: >> >>> 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. >>> >> >> -- > 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.
