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

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:
>
>> Hi,
>>
>> The order of include directories in a python extension matters to me.  The
>> advice  here:
>> http://lists.boost.org/boost-build/2011/02/24625.php
>>
>> 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
>>                   :
>>                        src/pyicl_module.cpp
>>                   :
>>                        <include>$(TYPE_TRAITS_DIR)&&$(BOOST_ROOT)
>>                       <use>/boost/python//boost_python
>>                        <define>PYICL_MODULE_NAME=_pyicl
>>           ]
>>           /boost/python//boost_python
>>       ;
>>
>>
>>
>> Thanks,
>> John.
>
> 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
> (<include>XXX&&$(BOOST_ROOT)).

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.

John.