Subject: Re: [Boost-build] order of include directories in python extension
From: John Reid (j.reid_at_[hidden])
Date: 2011-02-21 13:32:31
On 21/02/11 18:14, Gevorg Voskanyan wrote:
> John Reid wrote:
>> The order of include directories in a python extension matters to me. The
>> advice here:
>> doesn't seem to be working for me in a python extension. I.e. $(BOOST_ROOT) is
>> always before $(TYPE_TRAITS_DIR). Can anyone help?
>> My targets look like:
>> # Python interval container library extension
>> python-extension _pyicl
>> : # sources
>> obj pyicl_module
> Most likely<use>/boost/python//boost_python gives pyicl_module another
> <include>$(BOOST_ROOT) requirement (as one of boost_python target's usage
> requirements), which isn't under the ordering control unlike the other one
That's what I thought.
> 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? 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.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk