From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-01-20 07:20:21
On Wednesday 12 January 2005 06:00, Alexey Syomichev wrote:
> > My guess is that the problem is that inside 'a/Jamfile' you have twice a
> > target names 'a': the project and the library. Try to rename the project
> > to 'module_a' for instance or soth. and see what happens.
> Does the "project" rule generate any targets? I didn't think so.
> Anyway, I gave it a shot and renamed both projects. It didn't help.
> From looking at the error I can say that duplicate targets are actually
> created for the the same library with different sets of properties
> ("added properties: <define>B"). The other thing is that both
> conflicting targets are produced by the "stage" rule. The question is,
> why common%common.copy-a.STATIC_LIB is generated second time with the
> requirements of the project "b"?
That's the way the 'stage' rule works. It adds its own free properties to the
properties of copied targets. This behaviour is going to change very soon, so
OTOH, I think it's better to have a single "stage" rule at the top-level.
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