You need a separate procedure for Windows (if sys.platform=="win32") with something along the lines of the Windows installer for OB 2.2.0 Python at:
http://openbabel.svn.sf.net/viewvc/openbabel/openbabel/tags/openbabel-2-2-0/windows-vc2005/OBPythonOBF/setup.py?revision=2698&view=markup The extension modules in this case are not built with distutils and yet it all works. It's also possible to set some environment variables at this time, if necessary. See the postinstall.py script in the same directory. - Noel 2009/2/27 Greg Landrum <[email protected]>: > On Fri, Feb 27, 2009 at 10:08 AM, Noel O'Boyle <[email protected]> wrote: >> Yes - I was wondering how you were going to pull off the Windows >> release. If you want someone to bounce ideas off, get in touch... > > Thanks for the offer. > What I tried is to use the python distutils to create either a tar > ball (linux and mac) or a clickable installer (windows). This would > take care of installing the RDKit in appropriate directories. The few > dependencies (numpy, pil, etc.) could be pretty easily installed using > other standard python tools (e.g. setuptools). > > The problem is that though distutils is quite good at installing > extension modules that are built using distutils, it seems to be much > weaker at installing extension modules that are built using some other > method (i.e. bjam, cmake, whatever). Essentially what happened is that > the windows installers that I'd get would end up putting the .py files > in the right place, but they'd screw up the location of the .pyd files > for the RDKit extension modules. This didn't happen on linux or the > mac. Unless I can find some time to look for work-arounds, I'm > probably just going to abandon the "simple windows installation" idea > and go back to a well-packaged zip archive (or tarball) that the user > can just extract in the appropriate place. > > Alternate suggestions are very welcome, > -greg >
