Re: How to stop a variable from being exported?

[Alexey Neyman]

FWIW, I just missed the MAKEOVERRIDES variable and, assumed the
"MAKEOVERRIDES := $(filter-out selector=%,$(MAKEOVERRIDES))"
construct does, am happy with such way.

On Wednesday 27 October 2004 21:50, Boris Kolpackov wrote:
> Paul D. Smith <address@hidden> writes:
> 
> > When you invoke a make with a specific value like this:
> >
> >     make selector=abc
> >
> > then the variable override static string "selector=abc" will be 
passed
> > to every submake.  Whether you set your local copy of the 
"selector"
> > variable in that version of make doesn't change the value of the 
command
> > line string passed to sub-makes.
> 
> Not that I insist it's a bug, but, IMO, this logic is strange. When 
I say
> 
> override selector=cba
> 
> I would naturally expect the new value in every place that 
originated
> from this makefile. Also I can't think of any scenario where current
> logic might be useful.
> 
> -boris
> 

-- 
But wait!
This doesn't have to be the end!
                        -- Pkunks, SC2