From: Daniel Schlyder (daniel_at_[hidden])
Date: 2006-06-30 08:24:29
Johan Nilsson wrote:
> Johan Nilsson wrote:
>> Daniel Schlyder wrote:
>> Anyway, adding a common prefix to your modules might make sense as a
>> crude way of getting away without support for nested modules (which I
>> is unavailable).
Hmm, yeah. I guess I could do that.
>>> Anyway, it doesn't solve the real issue, which is that I previously
>>> didn't have to qualify rule name passed to <tag>, but I now have to,
>>> the rule is defined in another module
>> Can you try to import the rule into the global module?
> IMPORT tag : my-tag : : my-global-tag-alias ;
I get the following error:
IMPORT error: rule "my-tag" unknown in module "vendor/bbext/tag."
import vendor/bbext/tag : my-tag : my-global-tag-alias ;
works, though, but I can't use my-global-tag-alias without qualification
as argument to <tag>. I've worked around it for now. More pressing
issues. ;) Thanks for trying to help!
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