Re: [Boost-build] [bbv2] Build-dir for used projects

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-07-12 02:11:07

On Thursday 29 June 2006 12:08, Johan Nilsson wrote:

> I actually just now tried this before 'use-project' boost :
>
> local argv = [ modules.peek : ARGV ] ;
> argv += --builddir=$(mybuilddir) ; # need to check if it already exists
> modules.poke : ARGV : $(argv) ;
>
> But the build-dir didn't change. Checking the root Jamfile.v2 showed that
> it was hard-coded to bin.v2 - which I guess was what you were saying all
> along. Just to make sure it worked as expected, I tried the same thing with
> '--without-python', and that worked fine.
>
> Looks like a bug to me - the command-line option '--builddir' doesn't seem
> to be respected. At least not in my week-old copy of RC_1_34_0.

Well, there's no such option ;-) Looking at 
http://boost.org/boost-build2/doc/html/bbv2/advanced/invocation.html

I see option name "--build-dir", though. 

I must admit using command line option like that, in the middle of Jamfile, 
might not work. If you have a suggestion on a clearer solution, I'd be 
interested to hear.

- Volodya

-- 
Vladimir Prus
http://vladimir_prus.blogspot.com
Boost.Build V2: http://boost.org/boost-build2