[Python-Dev] Windows make_buildinfo changes in 2.6 and cross-compilation (original) (raw)
Tim Lesher tlesher at gmail.com
Fri Dec 4 23:01:48 CET 2009
- Previous message: [Python-Dev] Summary of Python tracker Issues
- Next message: [Python-Dev] who wants to be sprint coach @ PyCon 2010?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I ran across this while trying to upgrade our company's internal Windows CE build from 2.5.2 to either 2.6 or 3.1.
In the 2.5 era, the Windows version of make_buildinfo used to fall back to just copying the getbuildinfo.c file from \Modules if subwcrev failed; since 2.6, make_buildinfo fails the build if the compilation of getbuildinfo.c fails when make_buildinfo is run, without falling back to copying.
Any reason not to keep the fallback strategy in the process?
The new process fails in cross-compilation scenarios (like building for Windows CE on a Windows host) because, while the VC++ solution can be told to build native (win32) binaries for make_buildinfo and make_versioninfo, when make_buildinfo tries to compile via its hardcoded call to cl.exe, it tries to use the cross-compiler without the required flags from the cross-compilation configs in the vcproj files.
Thanks!
-- Tim Lesher <tlesher at gmail.com> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20091204/4ee6b969/attachment.htm>
- Previous message: [Python-Dev] Summary of Python tracker Issues
- Next message: [Python-Dev] who wants to be sprint coach @ PyCon 2010?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]