Great -- thanks for the feedback. That bug report is generally what
I've suggested too, so we're on the right track.
I will work up a patch for this, but to make sure that the patch will
work on all platforms, I could use a little help.
Specifically, if folks could run the following python commands and
send me the output (it could be quite long -- no need to cc the CMake
list), I would be able to get this patch working. I would also need
to know what platform you're on, and what the correct
PYTHON_INCLUDE_PATH, PYTHON_LIBRARY, and PYTHON_DEBUG_LIBRARY values
are that FindPythonLibs generates now.
Python code:
import distutils.sysconfig
print distutils.sysconfig.get_python_version()
print distutils.sysconfig.get_python_inc()
print distutils.sysconfig.get_python_lib()
print distutils.sysconfig.get_config_vars()
Finally, does windows python use UNIX-style command-line switches
(e.g. 'python -c' or windows-style switches 'python /C'?
Zach
On Jan 16, 2006, at 6:13 AM, Brad King wrote:
Zachary Pincus wrote:
I've been playing with using Python itself within a CMake file to
look up include directories for python extensions. (e.g. query
the Numeric module within python to find the Numeric C header
file's location.)
It occurred to me that this might be a better way for
FindPythonLibs.cmake to work too.
[snip]
Is this worth pursuing? I could try to work up a patch if anyone
thinks this is valuable.
There is a bug report suggesting a better way to find Python already:
http://www.cmake.org/Bug/bug.php?op=show&bugid=2257&pos=0
but no one has taken the time to implement it. If you are working
on a better FindPythonLibs please look at this link for suggestions.
Thanks,
-Brad
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake
