On Thu, Jan 21, 2010 at 2:23 PM, Greg Landrum <[email protected]> wrote: > On Thu, Jan 21, 2010 at 11:32 AM, Gianluca Sforna <[email protected]> wrote: >> For python, it seems you need to set PYTHON_INCLUDE_PATH and >> PYTHON_LIBRARY in order to use your own version > > exactly, and that's what the "hackery" code in the file does. If there > is a better pattern for doing this, I'm happy to hear it. Using ccmake > isn't a good general purpose option because I think that would prevent > the build from being done by a script in the case where one needs to > use a non-standard version of python.
I think you can do it with regular cmake using something like: cmake -DPYTHON_LIBRARY=/path/to/python/shared/or/static/lib -DPYTHON_INCLUDE_PATH=/path/to/pyhton/include/files I haven't a alternate python install to test it, though -- Gianluca Sforna http://morefedora.blogspot.com http://www.linkedin.com/in/gianlucasforna ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Rdkit-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rdkit-discuss
