From: Rob Stewart (rob_stewart_lists_at_[hidden])
Date: 2005-08-25 21:01:48
Larry Evans wrote:
> On 08/24/2005 02:24 PM, Rob Stewart wrote:
>>Is there a recommended way to develop a new Boost library
>>alongside a Boost release? IOW, I have Boost 1.33 installed. I
>>want to develop a new library to be part of Boost, so I need to
>>lay it out as if it were part of Boost, but I don't want to put
>>it in the Boost 1.33 tree.
>>How to I set up Jamfiles, etc., so that my separate tree builds
>>properly, including BoostBook? As I have things now, I expanded
>>Boost 1.33 into boost_1_33_0, which is a sibling of the directory
>>in which I've put the new library code. I want to be able to run
>>bjam --v2 in the new library's doc subdirectory for QuickBook and
>>I want to be able to install the library headers.
> My development tree is:
> sandbox //this is where I put development directories
> torjo //where, for example, I've downloaded John Torjo's rangelib
> lje //this is where I do my development
> Jamfile.v2 //this *file* "connects" lje to boost_1_33_0 to
> //make it appear part of boost.
> //This is done with contents:
Thanks. I'll do that if no one else steps forward with a better
solution. What I dislike about your scheme is that updating to
1.33.1, for example, means having to move all of the sandbox
files from one tree to the other. OK, that's not a big deal, but
I was hoping for a solution whereby the new code would be in a
separate tree, but tied into it. Then, switching to a new tree
would involve just modifying a Jamfile, if I'm right.
I'll see if your Jamfile provides clues for doing so.
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