Re: [Boost-build] Order of include directories in Boost Build

Subject: Re: [Boost-build] Order of include directories in Boost Build
From: Edward Diener (eldiener_at_[hidden])
Date: 2011-02-11 10:39:49

On 2/11/2011 3:37 AM, Vladimir Prus wrote:
> On Friday, February 11, 2011 01:31:07 Edward Diener wrote:
>> In a sandbox project, which has many of the same header files as a
>> same-named Boost distribution directory, I want to run the tests so that
>> the include directories are picked up first from the sandbox project and
>> then from the Boost distribution which BOOST_ROOT and/or BOOST point to.
>>
>> I even put a jamfile in the top-level sandbox directory which is:
>>
>> project sandboxlibrary
>>
>>       : requirements
>>
>>           <include>.
>>           <include>$(BOOST_ROOT)
>>
>>           build-dir bin.v2
>>       ;
>>
>> Yet when i try to run the tests the include directory order is:
>>
>> "-IC:\Programming\VersionControl\boost"
>>
>> "-IC:\Programming\VersionControl\sandbox\sandboxlibrary"
>>
>> In other words Boost Build is setting up the command line so that the
>> Boost distribution comes before the sandbox directory when looking for
>> include files. Naturally this causes the tests to fail since the changes
>> in the include files are not being picked up from the sandbox directory
>> first.
>>
>> Is this a deficiency or a bug in Boost Build ? Is there any way to work
>> around this problem ?
>>
>> It does seem as if one should always be able to run Boost Build from an
>> outside directory not within a Boost distribution, still picking up
>> files as necessary from a Boost distribution, and having the sandbox
>> files found first before the Boost distribution files.
>
> Please try:
>
> 	<include>.&&$(BOOST_ROOT)
>
> The jury is still out as to whether requiring to explicitly specify order
> in such cases is good or bad idea.

Why do you say that ? It is obvious that the order of include 
directories is very important.

That did fix the problem, when I finally noticed that the sandbox 
library whose tests I was trying to run had a project-root.jam file that 
had to be manipulated correctly.