Boost logo

Boost-Build :

From: timgift (timgift_at_[hidden])
Date: 2005-08-02 20:16:44

I forgot to point out that each library typically has several platform
specific sub-directories, so the Jamfile count gets high pretty quick.

Even with them all in one Jamfile, it seems like I would still need
individual projects for each library's platform code, and merge them
in to the main library? ...

Directory structures are basically:

+ root
+ Lib1
+ win32
+ posix
+ osx
+ sub-module1
+ sub-module2
+ Lib2


--- In jamboost_at_[hidden], "timgift" <timgift_at_y...> wrote:
> I have a c++ project which consists of a collection of 9 libraries and
> 4 executables. Each library is fairly small (they average around 20
> files each), and the tools are typically one or two source files. I'm
> currently using Perforce jam and find it very convenient to have the
> complete project in a single Jamfile, which is only 300 or so lines
> long. I do a fair amount of refactoring, moving files around, etc.,
> and having a single Jamfile makes life a lot easier. The alternative
> is 20+ Jamfiles, which seems a little overkill.
> I've tried getting v2 to compile everything from a single
> Jamfile, but using a single Jamfile project with multiple lib targets
> is not practical because of numerous file name collisions (see
> notes/relative_source_paths.txt).
> A possible solution is to allow multiple projects in a Jamfile, but so
> far that doesn't seem possible... does anybody know if this is
> possible? I'd basically like to have a single Jamefile something like
> this:
> project util : source-location util ;
> lib util : a.cpp b.cpp ;
> project kernel : source-location kernel ;
> lib kernel : a.cpp b.cpp c.cpp ;
> project tool : source-location tool ;
> exe tool : tool.cpp /util//util /kernel//kernel ;
> Thanks!
> Tim


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at