On Thu, Jun 25, 2009 at 9:35 PM, Steve Borho<st...@borho.org> wrote: > On Thu, Jun 25, 2009 at 2:31 AM, Adrian Buehlmann<adr...@cadifra.com> wrote: >> On 25.06.2009 08:48, Steve Borho wrote: >>> I'm in the middle of migrating my nightly build process to a vista 64 >>> box and it's not quite ready to go yet. I'm switching over from MinGW >>> to MSVC (8.0) 2005 SP1 to build both Mercurial and the shell >>> extension, since I believe that was the compiler used to build Python >>> 2.5, and also because it is the only version I have access to. >>> >>> Near as I can tell, the free express version of VC9 does not support >>> x64 targets, and I'm not ready to plop down $300 for a developer >>> license. >> >> I have added a couple of instructions on how to build >> the shell extension at >> http://bitbucket.org/tortoisehg/crew/wiki/ShellExtension >> >> The free Visual C++ Express 2008 can be used to build the >> 32-bit target without any problem (thanks to the file >> "Makefile.nmake" contributed by Sune). >> >> There is also a section on 64-bit cross compiling. >> >> Jens Huebel seems to have succeeded at getting the free >> MS 64-bit compiler working with VC Express. He wrote how >> he did it at: >> >> "Visual C++ 2008 Express Edition And 64-Bit Targets": >> http://jenshuebel.wordpress.com/2009/02/12/visual-c-2008-express-edition-and-64-bit-targets/ >> >> I haven't tried that (warning: lengthy). >> >> Also, the shell extension still compiles >> with MinGW for the 32 bit target (install MinGW and do "make"). >> Just note that the size of the dll produced by MinGW is roughly >> four times the size of the dll produced by VC. > > Well the oddessy continues today. I did get my hands on a VC8 install > CD and put it on my x64 dev box, but a simple 'python setup.py > install' inside the Mercurial repository failed to build extensions. > After reading the Mercurial Wiki and googling around and trying a > half-dozen remedies (including hacking directly on distutils for a > while), I gave up trying to get the combination to work. > > It seems 2.5 distutils is just not aware of x64 (and the SYSWOW > nonsense) and has too many hard-coded file and registry paths. So I > updated to Python2.6 and then updated pygtk, pywin32, and py2exe for > 2.6 and then tried again. > > Unfortunately I was still confounded. Python2.6 seems to want VC9 on > x64 in order for the path and registry lookups to work. So I'm now in > the process of installing VC9 (MSVC2008) and we'll see whether this > works at all. > > If there are any more hitches at all I'm going to be forced to move > back to my x32 machine for building the installers. This would be > doable, but annoying as I'm trying to retire this machine since it's > hard-drive has started to become unreliable.
Even VC9 would not build extensions, so I've decided to stick with Python 2.5.4 and VC8 for the 0.8.N releases. We have till 0.9 in November to work the kinks out of building an installer on an x64 machine. I'll try to get a nightly build out today. -- Steve Borho ------------------------------------------------------------------------------ _______________________________________________ Tortoisehg-discuss mailing list Tortoisehg-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
