In article <[EMAIL PROTECTED]>, Giovanni Bajo <[email protected]> wrote: >>> It's theoretically possible, but pratically very difficult to implement. >>> There are many implicit/explicit assumptions that the version of Python >>> with which you're running Build.py it's the same with will be contained >in >>> the final package, and this pretty much defeats cross-compiling. Notice >>> that, for this reason, it is equally hard to use e.g. Python 2.3 to >>> package a Python 2.4 binary. >> >> This is actually not a problem at all. I'm willing to locally build a >> Python version that exactly matches the cross-built version. Other >> than that, are there obstacles? For example, does PyInstaller rely on >> reflection to decide which modules to package? > > >No it does not use introspection, it parses the bytecode to walk the import >chain (see mf.py). > >There are many is-windows / is-linux kind of tests which uses the os.name / >sys.platform and so on. You will have to change all of them so to reflect >the target platform rather than the current platform. If you want to work on >this, I'd be happy to provide some support, but you'll have to work around >obstacles yourself. Patches are welcome!
OK, just for my understanding: is there also a possibility to build installers GUIs a la NSIS? I'll have a look at the platform tests time permitting. _______________________________________________ PyInstaller mailing list [email protected] http://lists.hpcf.upr.edu/mailman/listinfo/pyinstaller
