ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> cpp-sig
cpp-sig
Re: [C++-sig] Boost V1 build on Solaris
by David Abrahams other posts by this author
Nov 6 2002 8:01PM messages near this date
Re: [C++-sig] Boost V1 build on Solaris | Re: [C++-sig] Boost V1 build on Solaris
"Paul F. Kunz" <Paul_Kunz@[...].EDU>  writes:

>     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?

Sorry it took so long to come up with an answer, Paul. It was staring
me right in the face the whole time, though:

You just need to make sure your PYTHON_INCLUDES variable has two
elements. Depending on how your shell treats quotes, that could take
several forms. The shells I have available, e.g. bash, will let you
embed a space in a command-line argument as follows:

bjam -sPYTHON_INCLUDES="/afs/.slac.stanford.edu/package/python/common/2.0/include /afs/.slac
.stanford.edu/package/python/sun4x_55/2.0/include" ...

And bjam splits up variable values on whitespace boundaries.

Some shells let you set up variables with embedded spaces in the
environment; you might try that if your shell doesn't cooperate when
you try to use quotes in the command-line.

-- 
                    David Abrahams
dave@[...].com * http://www.boost-consulting.com


_______________________________________________
C++-sig mailing list
C++-sig@[...].org
http://mail.python.org/mailman/listinfo/c++-sig
Thread:
Paul F. Kunz
Paul F. Kunz
David Abrahams
Leonardo Rochael Almeida
David Abrahams
David Abrahams
David Abrahams
David Abrahams
Leonardo Rochael Almeida
David Abrahams
Paul F. Kunz
David Abrahams
Paul F. Kunz
Paul F. Kunz

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved