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

Subject: Re: [Boost-build] Library or tool outpath path
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2016-03-09 18:28:15

AMDG

On 03/09/2016 03:48 PM, Edward Diener wrote:
> 
> 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 ?
> 

  To support --libdir, it should use package.install.
Explicitly handling --libdir would also work:

local libdir = [ option.get libdir : ../../../dist/lib ] ;
... <location>$(libdir)

> 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.

  --build-dir is used for anything that doesn't
specify an explicit <location>.

> Surely I should be able to tell the install target where I
> want the final exe to be copied to.
> 

In Christ,
Steven Watanabe