Re: [Boost-build] Library or tool outpath path

Subject: Re: [Boost-build] Library or tool outpath path
From: Vladimir Prus (vladimir.prus_at_[hidden])
Date: 2016-03-09 02:20:50

On 09-Mar-16 9:45 AM, Edward Diener wrote:
> On 3/8/2016 11:34 AM, Steven Watanabe wrote:
>> AMDG
>>
>> On 03/08/2016 08:54 AM, Edward Diener wrote:
>>> When using b2 to build a particular non-header only library from that
>>> library's build directory, or when building a particular tool from that
>>> tool's build directory, is there a way to specify on the command line a
>>> final path where I want that library or tool to be copied to ? I tried
>>> using --prefix but it had no effect.
>>>
>>
>>    There should be stage and install targets
>> like at the top level, but I don't think
>> anyone uses them, so they might be broken.
>
> I am not invoking b3 from the top level but from the particular tool's build directory. Should stage and install targets
> work if not at the top level ?

Edward,

In Boost.Build, "b2 stage" or "b2 install" work iff project in the current directory has "stage" or "install" targets 
declared. Unlike make, we don't have a global namespace where all targets are dumped.

In Boost C++ Libraries, it's a good idea to have each component declare such targets - in particular for compiled
libraries we have 'boost-install' function that declares these targets. Possibly the library or tool you're working
with is not doing that?

Thanks,

-- 
Vladimir Prus
http://vladimirprus.com