Re: [Boost-build] order of include directories in python extension

Subject: Re: [Boost-build] order of include directories in python extension
From: Gevorg Voskanyan (v_gevorg_at_[hidden])
Date: 2011-02-21 14:08:12

John Reid wrote:

> > Try removing<use>/boost/python//boost_python to see  if it helps. If you 
need
> > boost_python's other usage requirements (if  any), consider specifying them
> > manually for pyicl_module.
> 
> So I  removed <use>/boost/python//boost_python and it didn't compile. Is 
> there a straightforward way to determine the usage requirements of 
> /boost/python//boost_python at build-time?

I'm almost sure there is a way, just not sure if it's straightforward. No idea 
what would be the recommended way, but using generate-dependencies rule from 
targets.jam in an indirect conditional requirements rule would be something I'd 
try first.

Then again you could try applying these usage requirements manually:
            <link>static:<define>BOOST_PYTHON_STATIC_LIB
            <python-debugging>on:<define>BOOST_DEBUG_PYTHON
, but yes, that might not be the best solution in the long run.

> If not then boost.build 
> doesn't seem to handle the order of #includes so well at the moment. It 
> is probably easier for me to arrange my include directories 
> alphabetically in the  filesystem.
> 
> John.

I am interested in learning the proper way to "determine a target's usage 
requirements at build time", too.

Gevorg