Has anybody built 2.3.4 on Win64, and if so, is there a preferred way? We built it by exporting the makefiles and twiddling with the linker options and pointer size in pyconfig.h, but that seems a bit kludgy. -- Nick
Nick Bastin wrote:
Has anybody built 2.3.4 on Win64, and if so, is there a preferred way? We built it by exporting the makefiles and twiddling with the linker options and pointer size in pyconfig.h, but that seems a bit kludgy.
I did (assuming you mean Itanium). I first tried it with that approach, then I talked Peter Tröger into developing vsextcomp, which is now used in the CVS. So unless you have a specific reason to use 2.3.4, I recommend to use 2.4. If I had to do it again, I would use a vsextcomp procedure now: Import the VC6 project files into VC7, then, using vsextcomp, generate Itanium targets for them. Regards, Martin P.S. sf.net/projects/vsextcomp
On Aug 11, 2004, at 2:20 PM, Martin v. Löwis wrote:
Nick Bastin wrote:
Has anybody built 2.3.4 on Win64, and if so, is there a preferred way? We built it by exporting the makefiles and twiddling with the linker options and pointer size in pyconfig.h, but that seems a bit kludgy.
I did (assuming you mean Itanium). I first tried it with that approach, then I talked Peter Tröger into developing vsextcomp, which is now used in the CVS. So unless you have a specific reason to use 2.3.4, I recommend to use 2.4.
I forgot to mention that the platform in question is AMD64, although we will be building on Itanium as well. Using 2.4 is not an option at this point. -- Nick
Nick Bastin wrote:
I forgot to mention that the platform in question is AMD64, although we will be building on Itanium as well. Using 2.4 is not an option at this point.
I'd still recommend vsextcomp. Copy the 2.4 project files to 2.3, and replace all occurrences of MS_ITANIUM with MS_OPTERON. Alternatively, create new AMD64 configurations, and contribute that to Python 2.4, then use the project files on 2.3. Regards, Martin
participants (2)
-
"Martin v. Löwis" -
Nick Bastin