From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-10-21 03:19:56
> I've just come across an alias rule limitation -- it does not copy
> usage-requirements. For example, suppose I have thirdparty library
> declaring two libs -- util and main. main has a usage-requirement
> <library>util. Now if I will declare an alias for main it will not
> copy usage-requirement, hence it will not work as an alias.
Confirmed as a bug.
> Not sure what is the right way to fix it, since not all targets have
Technically, all main targets have usage-requirements, even if empty, and
abstract-target.generate always return usage-requirements. It would be
possible to make "alias" combine usage requirements of all sources and return
them as usage requirements. Will it be OK?
If so, I can implement this one day soon. For now, I think you can workaround
alias b_alias : : : : <library>b ;
> To unsubscribe from this group, send an email to:
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
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