The exewrapper mini-project builds a xx.exe file for Python script xx on
Windows, which can be used instead of a xx.bat or xx.cmd file to call the 'xx'
The exe embeds the Python interpreter by dynamically linking to it. A separate
exe must be built for each major Python version, that is, a specific exe is
bound to python27.dll, or python26.dll etc.
If there is no xx file found in the same directory as xx.exe, then xx.exe tries
to start xxexe.py instead. This can be useful for cases where hiding away the
original xx script is needed.
The python script name called is inferred from the name of the exe: foo.exe
searches for python script foo and takes fooexe.py if foo doesn't exist in
the same directory as foo.exe.
To build exewrapper, Python must be installed. The makefile (Makefile.nmake)
only depends on the Windows SDK compiler toolchain , so no Visual Studio
is needed for building. This allows to build x64 and x86 exewrappers.
For building the exe, either start a shell using build32.cmd (to build the
x86 exe's), or build64.cmd (to build the x64 exe's) and then in either of
them execute build.cmd.
build.cmd at the moment assumes Python installs in:
so it currently supports building exewrapper's for these.