I suppose it :)

Well, I hope will exists such enhancement a day.

Regards,
    Daniele

Maybe it's a feature...but if so would be useful to have something (as a keyword) to resolve this "problem": when you set a target-specific variable value, that association is inherited into sub-targets.

This implies that the build will be target-specific: making target A and then target B build a different thing than making target B and then target A (in real compilations often only one of those is successful).

For example there are problems in building libraries: to compile the library LDFLAGS must not include, of course, the library itself, but to compile the programs that uses the library you must set it. If you build first the library and then the programs all works, but if you build the program and "make" try to rebuild the library (because it not exists or is out of date), then the wrong LDFLAGS will be inherited breaking the compilation.

In attachment you find a simple Makefile that shown the behaviour with LDFLAGS: if you invoke "make library" and then "make program" the file "library" will contains "none" and the file "program" will contains "library" (ok), but (after "make clean") if you invoke "make program" then both files "library" and "program" will contains "library", that it's not right.