From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-07-22 04:45:57
On Thursday 29 June 2006 19:10, Phillip Seaver wrote:
> Johan Nilsson wrote:
> > Phillip Seaver wrote:
> >> 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?
> > // Johan
> Well, I just changed the name back and my project failed to build. I
> added a path constant in my Jamroot.jam that the boost jamfile.v2
> doesn't see, for whatever reason. I was trying to build a separate
> project that uses boost, so it wasn't that I was in the boost directory
> and it didn't see my Jamroot.jam.
> I hadn't thought of trying to modify ARGV to change the build
> directory. Sneaky, but in a good way. :->
> To the developers: would it make sense to have a "default-build-dir"
> that is used if the parent doesn't set it? That way, people could build
> boost outside the source tree without having to remember to add
> "--build-dir" to their bjam calls (or use a script/alias/batch
The problem is that Boost has it's own project-root.jam, and so does not
inherit any properties of any projects. In fact, it inherits properties --
but from user-config.jam, not any your files.
There's really no mechanism to apply any properties to a project that has
Jamroot file (or in case of older projects, project-root.jam).
I tend to think that overriding --build-dir inside boost-build.jam for your
project is the most straight-forward solution.
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
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