Boost logo

Boost-Build :

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-12-07 06:51:41

On Tuesday 07 December 2004 14:25, Toon Knapen wrote:
> Vladimir Prus wrote:
> > Thanks. Running this testcase with a slighly modified V2 (with added
> > diagnostic), I get:
> >
> > Building algorithm with
> > Common-properties are <debug-store>object ..... <parallelism>none
> > ........
> I just updated my bjam. So how the see the information you mention here
> (i.e. the properties used to build the 'algorithm' target) ?

It was not committed yet. I've a bit improved it (nice indents) and committed
now. Just add --debug-building option to bjam.

> > which means the 'algorithm' target is built with <parallelism>none, so is
> > not linked to *any* library.
> I thought that the 'algorithm' target would inherit the
> <parallelism>fake feature because it links to the 'libfemtown_std'
> library which is build with the '<parallelism>fake' feature.
> But also adding <parallelism>fake to the requirements of the 'algorithm'
> target still does not result in linking 'algorithm' with the fake-mpi
> library ?!

I wonder if it's caused by this:

feature.compose <parallelism>fake :
<library>$(CVSTOP)/fake_mpi//libfake_mpi/<parallelism>none ;

CVSTOP = [ modules.peek : CVSTOP ] ;

You use CVSTOP before definition. If I use:

feature.compose <parallelism>fake : <library>/femtown//fake_mpi ;
lib fake_mpi ;

the application links to fake_mpi. (Somehow it links to it twice, but that's
another thing. I'll look into it)

- Volodya


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