From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-12-08 01:24:14
> Am Freitag, 5. Dezember 2003 18:10 schrieb Pedro Ferreira:
> > I found a problem that causes a 'Duplicate name of actual target'
> > error (I really can't remember if this has already been brought up by
> > anyone).
> I doubt this.
In fact, this is
Going back to Pedro's example:
lib a : A1/A.cpp A2/A.cpp : <link>static ;
stage stage : a ;
I am not really sure where to compile those different A.cpp, so that they
don't conflict. One solution, from
would be to create auxilliary obj targets:
obj a1 : A1/A.cpp ;
obj a2 : A2/A.cpp ;
and then use them. Whether it can be automated, how it can be automated and
whether it's worth the effort are the questions.
> I've got a similar problem. This appears after the virtual target
> changes. I should have tested on Win32, too.
> Sorry, Volodya !
> I specify
> lib alib : : <name> a.lib ;
> alias a : extra.obj allib;
> and on toplevel Jamfile, a similar message appears.
I suspect this might be a different problem. I simplified generation of actual
target names to fix some other bug, so we might got this regression.
> Building from sub-projects works fine.
> > Any hope of solving this easily?
> I could try to build a test case on Monday if needed.
That would be very appreciated!
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