From: Johan Nilsson (r.johan.nilsson_at_[hidden])
Date: 2006-06-30 08:38:20
Daniel Schlyder wrote:
> 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 think
>>> 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, if
>>>> 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
> as argument to <tag>.
IMPORT and import are different rules. The former is a built-in, while the
latter is not.
Note the blank between two ':'s in the IMPORT statement I wrote above. That
argument refers to the target module for the import, which, when left empty,
refers to the global module.
Try to rename your module to e.g. vendor-bbext-tag.jam and add its path to
BOOST_BUILD_PATH, then do:
IMPORT vendor-bbext-tag : my-tag : : my-global-tag-alias ;
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