Re: [Boost-build] Cuting project in pieces

Subject: Re: [Boost-build] Cuting project in pieces
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2011-02-07 11:30:13

AMDG

On 2/7/2011 1:13 AM, Samuel Debionne wrote:
> Hello boost builders,
> We are using boost build to build our own project including all third
> party libraries that we depend on (lapack, hdf5, szip...). It is a bit
> of work to maintain the jamfiles in sync for these libs but we manage...
> The question is : we now have a very large amount of targets in the same
> build system and incidentally a large number of "patience...". Is there
> a way to split a large project into different project that could be
> build "independantly" (leave in different root dir) and yet have the
> dependancies and properties set correctly on dependent projects ?

Splitting up the directories shouldn't matter.
Boost.Build only loads the Jamfiles that are
needed and it will load them regardless of
where you put them.

> Or
> asking in a more open manner, what should I try to improve the
> performance (the startup) of the build system ?

The only way to do this that I know is to stop
tracking dependencies through dependent projects.
Basically, you would need to create a forwarding
Jamfile like:

if --track-all-dependencies in [ modules.peek : ARGV ]
{
     use-project mylib : path/to/mylib ;
}
else
{
     project mylib ;
     searched-lib mylib : : <search>... : : /usage-requirements/ ;
}

Then you can refer to the library as /mylib//mylib.

> I read that ryppl seems to go for CMake. Is there a future for boost
> build (we really hope so) or shall we anticipate a move to an other
> build system (i.e. gyp) ?
>

In Christ,
Steven Watanabe