Pyinstaller works fine on Windows XP. I am trying to get it working on WINE. Running configure.py results in asking for pywin32, however pywin 32 will not install
C:\pywin32-214>c:\python26\python setup.py Building pywin32 2.6.214.0 This is a distutils setup-script for the pywin32 extensions To build the pywin32 extensions, simply execute: python setup.py -q build or python setup.py -q install to build and install into your current Python installation. These extensions require a number of libraries to build, some of which may require you to install special SDKs or toolkits. This script will attempt to build as many as it can, and at the end of the build will report any extension modules that could not be built and why. Currently, the Vista SDK and DirectX SDK are required to successfully build all extension modules - note that using the Vista SDK doesn't force you to use Vista as your build environment. Please use google to find the SDK - links to microsoft.com seem to only stay current for a short time. Also note that the SDK that comes with VS2008 is not good enough to compile earlier versions. If you installed VS2008 after the Vista SDK, try doing a 'repair' on your SDK install. Early versions of certain Windows headers/SDK versions will also cause certain modules to be skipped. If you don't use the extensions that fail to build, you can ignore these warnings; if you do use them, you must install the correct libraries. The 'exchange' extensions require headers that are no longer in any current SDKs, so these fail to build, but the 'mapi' extension should still build. Building: --------- To install the pywin32 extensions, execute: python setup.py -q install This will install the built extensions into your site-packages directory, create an appropriate .pth file, and should leave everything ready to use. There is no need to modify the registry. To build or install debug (_d) versions of these extensions, ensure you have built or installed a debug version of Python itself, then pass the "-- debug" flag to the build command - eg: python setup.py -q build --debug or to build and install a debug version: python setup.py -q build --debug install To build 64bit versions of this: * py2.5 and earlier - sorry, I've given up in disgust. Using VS2003 with the Vista SDK is just too painful to make work, and VS2005 is not used for any released versions of Python. See revision 1.69 of this file for the last version that attempted to support and document this process. * 2.6 and later: On a 64bit OS, just build as you would on a 32bit platform. On a 32bit platform (ie, to cross-compile), you must use VS2008 to cross-compile Python itself. Note that by default, the 64bit tools are not installed with VS2008, so you may need to adjust your VS2008 setup. Then use: setup.py build --plat-name=win-amd64 see the distutils cross-compilation documentation for more details. Standard usage information follows: usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: no commands supplied C:\pywin32-214>c:\python26\python setup.py -q install Building pywin32 2.6.214.0 error: Unable to find vcvarsall.bat C:\pywin32-214> -- http://mail.python.org/mailman/listinfo/python-list