From: slabman_meathouse (matthew.comi_at_[hidden])
Date: 2005-08-03 21:07:43
I have a Make build environment that I would like to migrate to BBv2.
My current environment is as follows:
Each project sits in a seperate directory, e.g. (reuse, product_a,
Each project consists of a collection of nested category directories.
A category directory contains a single class (header and cpp) and a
cppunit test harness. Categories may be nested when logically grouping
a bunch of similar classes.
Now onto my BBv2 migration...
My first attempt was to create a Jamfile per project, containing a lib
target archiving each category's class cpp file.
Each category also contains a Jamfile. This Jamfile contains a test
target, which included every cpp in the category (test_runner,
test_foo, foo) as well as requiring the project to which it belonged.
Does this sound sensible so far?
I am hoping that there is a way to ensure that the project will build
all of its categories without needing to be updated each time I create
a new category in that project.
If it were a flat directory structure, I realise it would be as simple
as putting a type of glob *.cpp (excluding test_* somehow) in the
project Jamfile. But I would rather not sacrifice the directory
Thanks in advance,
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