Re: [Boost-build] Pointing to a Boost tree for bjam

Subject: Re: [Boost-build] Pointing to a Boost tree for bjam
From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2010-11-16 10:53:51

On 16/11/10 15:24, Edward Diener wrote:
> On 11/16/2010 4:15 AM, John Maddock wrote:
>> In addition the variables BOOST and BOOST_ROOT are set to point to the
>> root of the Boost install, so to refer to other
>> Boost libraries and the main Boost headers, your Jamfile should contain
>> something like:
>>
>> import modules ;
>>
>> local boost-path = [ modules.peek : BOOST ] ;
>>
>> And then you can refer to a Boost library "foo" as:
>>
>> $(boost)/libs/foo/build//boost_foo
>
> Should not this be:
>
> $(boost-path)/libs/foo/build//boost_foo
>
>>
>> Note that if your project does not specify a Jamroot file, then a
>> default one is provided for you,
>> and that this file will automatically add $(BOOST)/ to your include
>> path."
>>
>> In other words the machinery in the root directory of the sandbox will
>> take care of almost everything for you - all you need to do is set the
>> BOOST environment variable -
>
> OK. But if the sandbox library is then moved under a Boost installation,
> does all this machinery continue to work as expected ?

Perhaps it's of little relevance here or it might actually be useful:

[boost] How to specify Boost headers location properly

http://lists.boost.org/Archives/boost/2010/03/162907.php

where env variables versus project and symbolic targets have been 
clarified to me.

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Member of ACCU, http://accu.org