Re: [Boost-build] Pointing to a Boost tree for bjam

Subject: Re: [Boost-build] Pointing to a Boost tree for bjam
From: Anthony Foglia (AFoglia_at_[hidden])
Date: 2010-11-17 11:02:03

Edward Diener wrote:
> Often I will get some sandbox library into a separate directory from the 
> latest Boost trunk using SVN. I then want to use Boost build to create 
> docs or run tests using this sandbox library. But efforts fail unless I 
> put the library under a Boost implementation or my own latest Boost 
> trunk because, evidently, bjam can not find the rest of Boost in which 
> the sandbox build(s) depends.
> 
> Of course the way I have been getting around this is to move the sandbox 
> library into the appropriate directory structure under my copy of Boost 
> trunk. This seems onerous, especially because I have to end up removing 
> any .svn directories for the sandbox library from Boost trunk directory 
> as not to confuse SVN.

How is SVN confused?  This is how we've been handling our sandboxes in 
our code base.  (For simplicity.  I don't like it for the same reasons 
you do.)  And we haven't had any problems with svn.

> Is there a better way ? Can I not somehow point to my Boost trunk from 
> within my sandbox directory structure to be able to build sandbox docs, 
> libraries, and tests without having to move my sandbox files into the 
> appropriate place under my latest copy of Boost trunk ? It does seem as 
> if Boost Build should be flexible enough to allow this. I do have my 
> user-config.jam and site-config.jam in my %HOMEDRIVE%%HOMEPATH%.

I'm not sure what is in your sandboxes, and if you need the Boost source 
from trunk, but if not, there is an jamfile someone created for setting 
up rules for Boost in a separate project.  It's relatively simple,

http://svn.boost.org/svn/boost/trunk/tools/build/v2/contrib/boost.jam

It looks relatively straightforward, but it's become out of date.  In 
addition to easily fixable issues I made a bug report for last year 
(plus any additional libraries), there was the change in the Boost 
library naming that needs to be reflected.  Here's my bug report.

https://svn.boost.org/trac/boost/ticket/3173

-- 
Anthony Foglia
Princeton Consultants
[phone] x233