[jamming] locals not local

[Craig Allsop]

> > Ok, maybe you're right, but have you never set a var on a pseudo
> > target? And then called a rule under the influence of that pseudo
> > target? This is a very useful feature!
> > In this way, I don't need to modify the stock jambase and use
> > "$(project)-DEFINES" or similar.
>
> Agreed. but I said, it's a matter of taste. The jambase that I have
> has barely any resemblance to the original one, so I don't care about
> modifying it, thus I fallback to the solution that I feel is more
> readable and easier to use for me. It's just an idea, I'm not saying
> it is "the right way". And in the end it seems that it is not related
> to what you had in mind.

I'd prefer to try and retain compatibility, maybe I'm crazy. Variables
per target (or pseudo target) is a wonderful concept. With Jam's built
in support to import a bunch of variables into a scope is just too
good to ignore IMO.

I do confess to tweaking Jambase but very little. In most cases just
to add a couple of variables that I can set per target. For example, I
changed the call to "Link" to "$(LINKRULE)" so I could set per target
link rule because the difference between platforms is too great. Such
a change could be incorporated into the stock jam simply by setting a
global LINKRULE = Link retaining compatibility.

Craig.