aboutsummaryrefslogtreecommitdiff
path: root/em++
AgeCommit message (Collapse)Author
2013-11-04[em++]: Removed unnecessary warning about the PYTHON variable ;Pierre Renaux
2013-08-09warn in em++ if PYTHON is not defined properlyAlon Zakai
2012-12-19Updated to add a PYTHON config option instead of defaulting to python2. This ↵Alan Kligman
should preserve the default behavior in a way that can be overridden.
2012-12-19Updated scripts to call python2 directly rather than relying on python ↵Alan Kligman
symlink pointing to the right place. See PEP394 for details on why this should be OK.
2012-03-20Misc fixes for Windows.Sigmund Vik
Most of these changes have to do with how python scripts are invoked. For Linux, 'Popen([EMCC] + args)' works because the first line in emcc is '#!/usr/bin/env python'. On Windows, the python interpreter has to be explicitly invoked, e.g. 'Popen(['python', EMCC] + args)'. Note that there is no harm in explicitly invoking the python interpreter on Linux, so this works on both platforms. For Windows, execvp() behaves differently than on Linux: http://mail.python.org/pipermail/python-list/2002-July/763863.html http://msdn.microsoft.com/en-us/library/3xw6zy53.aspx This causes many strange things to happen as the parent process terminated before its children. In this change the use of execvp() has been replaced with subprocess.call(). This change also fixes some code that assumed that the path separator always is '/', but for Windows it is '\'. And where the path module can be required, we use path.normalize() and path.resolve() to check if a filename is absolute in a platform agnostic manner.
2011-12-11emcc: --versionAlon Zakai
2011-11-22emcc stuffAlon Zakai