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

Subject: Re: [Boost-build] Library or tool outpath path
From: Edward Diener (eldiener_at_[hidden])
Date: 2016-03-09 17:48:24

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.

In the tool whose build jamfile I am looking at ( wave ) there is an 
install target. It's specifies a hardcoded relative directory. How can 
this be changed to use instead the --libdir value I pass to b2 on the 
command line ?

Needless to say the install hardcoded relative directory does not honor 
the fact that I might want my tool installed outside of the boost 
directory structure, and on another drive also.

The actual build from source of the exe does, automatically it seems, 
honor the --build-dir I also pass on the b2 command line, so the output 
files are generated in a totally other place outside the boost directory 
structure. Surely I should be able to tell the install target where I 
want the final exe to be copied to.