From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-12-23 11:30:46
On Thursday 23 December 2004 19:15, TEMPLIE Cédric wrote:
> > It is, indeed. But if ./project1 defines export_headers, export_lib and
> > project1 lib target, then project2 better link to "project1".
> > This way:
> > 1. If project1 is available you link directly to the library, not to the
> > staged version.
> > 2. If project1 is not available then Jamfile in $(STAGE_DIR) will define
> > project1 target and you will link to it.
> > Still no need to link to result 'stage' target.
> > - Volodya
> Yes, I agree, you mean what pedro said, linking directly with the
> lib project2
> : $(cppFiles:BS)
> : <source>/project1//project1
> But when doing that how to specify the project1 to also stage its
> headers and the generated lib in another location ?
If I were you, I would just create an "alias" at top-level Jamfile which would
have all "stage" target in individual projects as sources. Is there a problem
with that approach?
In theory, you should be able to use <dependency> on stage, but right now it
produces an error. Now that I've understood what you're trying to do, I'll
look at that error in detail.
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