Re: [Boost-build] project <tag> requires qualified name?

From: Daniel Schlyder (daniel_at_[hidden])
Date: 2006-06-16 10:34:28

Johan Nilsson wrote:
> Maybe you could try something like this:
> 
> ---
> #
> # project-root.jam
> #
> import modules ;
> 
> path-constant my-bbv2-ext-path : path/to/my/ext ;
> local boost-build-path = [ modules.peek : BOOST_BUILD_PATH ] ;
> boost-build-path += $(my-bbv2-ext-path) ;
> modules.poke : BOOST_BUILD_PATH : $(boost-build-path) ;
> ---
> #
> # Jamfile.v2
> #
> import tag ;
> 
> <tag>@tag.my-tag ;

Thanks! That's very interesting, but I can't do this, cause I have a 
utility.jam that would clash with the built-in module of the same name. 
I could, of course, rename that module, but then I might just have to do 
it again in the future. Does BB have something akin to Python's packages?

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.