Re: Scopes for rules

Bram Moolenaar wrote:
> The problem is not in Aap but in your recipe.
> 
> In your child recipe you only specify how to build "foo" from "foo.o".
> There is no rule to build "foo.o" from "foo.c".  When Aap figures out
> what to do, it sees that "foo.o" needs to be build and applies a default
> rule to compile it from "foo.c".  But this rule works at the toplevel,
> not in the child recipe.

Thanks - your reply helps, and I've got things working. :)

However - is there a reason why the rule has to work at the toplevel? 
Would it be possible to define default rules for which variables are 
evaluated at the level from which the rule was triggered, rather than 
that in which the rule was defined?

I imagine this would require redefining the order in which scopes are 
searched, and there may be consequences of this that I can't immediately 
see. However, I found the behaviour rather surprising, and am just 
wondering if there's a way to make it less surprising.


PS: any progress with my patch for the mingw tool?

-- 
Richard



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click