Граф коммитов

8 Коммитов

Автор SHA1 Сообщение Дата
Alon Zakai 16d378c78f do not use an env var to communicate c++ mode 2015-01-01 19:48:54 -08:00
Pierre Renaux 66d585fcd3 [em++]: Removed unnecessary warning about the PYTHON variable ; 2013-11-04 19:27:11 +08:00
Alon Zakai ae236b288c warn in em++ if PYTHON is not defined properly 2013-08-09 16:48:05 -07:00
Alan Kligman a2bc9a30de Updated to add a PYTHON config option instead of defaulting to python2. This should preserve the default behavior in a way that can be overridden. 2012-12-19 18:06:48 -05:00
Alan Kligman 315f13e5a1 Updated scripts to call python2 directly rather than relying on python symlink pointing to the right place. See PEP394 for details on why this should be OK. 2012-12-19 18:06:48 -05:00
Sigmund Vik f829735cc3 Misc fixes for Windows.
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.
2012-03-20 14:26:50 +01:00
Alon Zakai 58f694a190 emcc: --version 2011-12-11 10:23:03 -08:00
Alon Zakai 753437a56d emcc stuff 2011-11-22 21:34:03 -08:00