On Wed, 2002-10-23 at 22:36, Paul F. Kunz wrote:
>     One final question, which is not specific to boost::python but
>  general question on building Python modules.   What my Solaris
>  administrators have done is to configure Python with 
>  
>  >  ./configure
>   --prefix=/afs/.slac.stanford.edu/package/python/common/2.0
>   --exec-prefix=/afs/.slac.stanford.edu/package/python/sun4x_55/2.0
>  
>  They also did a build fron Linux with the appropriate `exec-prefix'.
>  What apparently this has done is to put all but one of the Python
>  include files in the directory `common/2.0/include'.  But Python.h
>  includes `config.h' or `pyconfig.h' (depending on the version) which
>  gets installed in `sun4x_55/2.0/include'.  This is appropriate since
>  this file is machine/OS dependent.
>  
>     Now the problem is that boost::python, and other packages, gives you
>  one variable, like PYTHON_INCLUDES,  for its build.   When it is set to find
>  `Python.h' it will not find `pyconfig.h'.   
>  
>     What is the best way to handle this situation?   Is it a bug in
>  Python's configure script?   Bug in boost::python and others?   Or am
>  I missing something obvious?

Your setup requires that sun4x_55/2.0/include is in the include path
somehow (i.e. it should be in the -I parameter of all compiler
invocations). Reading <boost> tools/build/gcc-tools.jam makes me believe
that you can make your setup work by adding the following line to your
<boost> /Jamrules file:

STDHDRS += /afs/.slac.stanford.edu/package/python/sun4x_55/2.0


IMO, the proper way to fix this would be to make boost.python accept a
PYTHON_EXECUTABLE variable which we could set like:

PYTHON_EXECUTABLE ?= /usr/local/bin/python2.2

This way, boost could probe python for its version and distutil
infrastructure for all apropriate include and link flags. This is what
Psycopg does in it's ./configure script (e.g. --with-python=...)

-- 
Ideas don't stay in some minds very long because they don't like
solitary confinement.


_______________________________________________
C++-sig mailing list
C++-sig@[...].org
http://mail.python.org/mailman/listinfo/c++-sig