From: Johan Nilsson (r.johan.nilsson_at_[hidden])
Date: 2006-06-29 04:08:49
Phillip Seaver wrote:
> Johan Nilsson wrote:
>> I'm using boost libraries from my own Jamfiles similar to the
>> path-constant build-root : ./build ;
>> project my-proj
>> : build-dir
>> use-project boost : $(BOOST_ROOT) ;
>> alias threads
>> : /boost/thread//boost_thread
>> : <link>static
>> However, I'd like the thread library to be built under $(build-root)
>> instead of $(BOOST_ROOT)/bin.v2. Is this possible without using
>> command-line arguments?
>> I was looking for some property that I could pass on using the alias
>> rule, but couldn't find anything.
>> // Johan
> I use boost from within my source tree and I ended up commenting out
> the "build-dir" in the boost Jamfile.v2, mainly because I wanted to
> everything outside of the source tree. I changed the "stage-locate"
> line to use my staging location instead of ./stage.
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.
> As a side note, I also renamed project-root.jam -- IIRC, it was
> interfering with using boost below my Jamroot.jam.
You don't happen to remember in what way ... now?
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk