Menu

Anyone successful with WinXP x64 build?

Help
Greg Smith
2009-03-31
2012-09-19
  • Greg Smith

    Greg Smith - 2009-03-31

    I have been extensively searching if this has been done before, so far however most of my efforts have been in vain. I was curious if anyone has had much success with this? The company that I work for is currently demoing new Compositing software (Nuke) and I am trying to establish pipeline tools in order to connect it to our own asset management database which is driven by MySQL. This hasn't been much of an issue in the past as to most of our software was x86 32bit, however since the compositing software has a 64 bit version, we want to make the best of it. Nuke natively uses python as a scripting language however due to the 64 bit nature, any compiled python tools must also be 64 bit as well.

    So I have tried to follow the compiling steps laid out in the Readme for 1.2.3b2 to compile for windows, however I keep getting an error stating:

    error: Python was built with Visual Studio 2003;
    extensions must be built with a compiler that can generate compatible binaries.
    Visual Studio 2003 was not found on this syste,. if you have Cygwin installed. you can
    try compiling with MingW32, by passing "-c mingw32" to setup.py.

    Now I have Visual Studio 2005 installed, would this be incompatible.

    Also I noticed in the build directory that the folder name had "win32" within it, does that mean its still trying to build a x86 build?
    If it isn't readily apparent, I am not much of a programmer, mostly scripting. So when it comes to compiling builds it can get confusing for me.

    Here's my setup:
    WinXP Pro x64 editition SP2
    AMD Opteron 2354
    ActiveState ActivePython 2.5.1.1
    MySQL 5.1.32-winx64
    MS Visual Studio 2005
    if I am forgetting anything else lemme know!

    Any help would be truly appreciated!

    thanks,
    Greg

     
    • Ioannis Lalopoulos

      Take a look at http://codegood.com/archives/4

      I have included 64bit and 32bit Windows builds for MySQLdb 1.2.2 and 1.2.3c1 (python 2.6.x).

       
      • Greg Smith

        Greg Smith - 2009-04-22

        very cool, do you know if there is a 2.5.1 build in existance? The reason I ask is that the module is mostly for use with our compositing software (Nuke) which runs its own embedded version of Python outside of the system install. It uses 2.5.1 for the current release, and I haven't looked around yet to see if another version of python can be installed.

        thanks!

        Greg

         
        • Ioannis Lalopoulos

          Just managed to make a 64bit build around Python 2.5.

          Build environment: 64bit versions of Windows XP Professional, Python 2.5.4, MySQL 5.1.33. and Windows Server 2003 SDK.

          I haven't tested it thoroughly yet, only the module loading, some basic attribute checkings and that it can be installed also in Vista 64bit.

          Unfortunately I don't have the time to publish it now due to an early morning business trip, but I will as soon as I get back this Thursday so that you can give it a try.

           
          • Greg Smith

            Greg Smith - 2009-04-28

            I truly appreciate all your efforts. This will help a lot.

            Thanks again,

            Greg

             
    • Ioannis Lalopoulos

      You can find the build you want at http://www.codegood.com/archives/72

      I hope it helps,

      John

       
      • Greg Smith

        Greg Smith - 2009-05-04

        seems that the .msi installer can't find the python version in the windows registry. No matter which flavor of 2.5 I have install on my machine.

        At first I was trying the standard install from python's website using
        python-2.5.1.amd64.msi to install. however It gave me the error:
        "Python version 2.5 required, which was not found in the registry"

        at first I might have thought I had a small issue with the fact that I also had a 32-bit version of activestate python 2.5.1.1 installed on my machine (need to develop for both platforms). So I removed the 32-bit install as well as the amd64 install of the standard python. Reinstalled the amd64 2.5.1 python. Same problem when I tried to install MySQLdb.

        Another test I tried was, installing the 64-bit version of the activestate flavor of python (2.5.1.1) hoping that my do something. Still no dice.

        So I don't know whats up to why it would give me grief. I've never really liked this about the MySQLdb installer that the user can't explicitly set where the install is. I've ran into this in the past with other modules that wanted to install in the 32-bit directory and wouldn't let me install in the 64-bit directory.

        So I don't know whats up, I am forwarding the problem on to our sys admin, but if there are any tips or work arounds that you might have to share, that would be great?

        Also I noticed you built against 2.5.4, would that be an issue? I am pretty sure it wouldn't be but I wanted to verify.

        Cheers,
        Greg

         
        • Ioannis Lalopoulos

          I forced this build with the 64bit installer exactly for this problem.

          In my system the default 64bit MySQLdb build was done with a 32 bit installer but my version of Python was installed with the 64 bit installer. I changed the installer version so that this problem would not show up, but it seems that in your case it was better to leave it with the default.

          Anyway the solution is easy:

          If python is installed with a 32bit installer the registry keys needed will reside at HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Python. You need to duplicate this info at HKEY_LOCAL_MACHINE\SOFTWARE\Python so that the 64bit installer can see it.

          (take note that HKLM and HKEY_LOCAL_MACHINE are the same thing)

          So the steps are:

          1. Take a backup of your registry

          2. Export HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Python (right click at it and select export).

          3. Edit the exported file in notepad and replace all instances of
            HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ with HKEY_LOCAL_MACHINE\SOFTWARE\ (take a final look at your changes to see that all - slashes etc - are correct).

          4. Import the file back to the registry

          You are done, this time the installer should see Python's installation.

          (Just to be sure that my initial observation was correct I uninstalled Python, deleted all Python registry keys, installed it again, verified that its registry keys are in HKLM\SOFTWARE\ and not in HKLM\SOFTWARE\WoW6432node, downloaded the installer from my site - to be sure that the correct version was up - and finally installed it without a problem).

          Good luck,

          John

           
          • Greg Smith

            Greg Smith - 2009-05-04

            Yep that did the trick! thanks very much for all the effort!

            Greg

             
  • Anonymous

    Anonymous - 2009-10-15

    I'm having the same problem. Here on a Windows 7 machine, with a AMD64
    processor. With Python 2.5.4 AMD64 installed. Annoying as hell.

     
  • Anonymous

    Anonymous - 2009-10-15

    5 minutes later: ilalopoulos: Your precompiled version worked excellently.
    Thanks!

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.