%% "Noel L Yap" <[EMAIL PROTECTED]> writes:
>> would give confusing answers. I'll think about this. You might
>> consider submitting an RFE to the bug tracking system.
nly> A possibly more general thing to do might be to keep the include
nly> stack within MAKEFILE. One should be able to get the current
nly> makefile with $(firstword $(MAKEFILE)). Anyway, just another
nly> consideration.
This is closer to what I was thinking. Although, I think they should
come in the order they were read, not in reverse order. Then the first
one is always the "main" makefile, and the last one is always the
current makefile. Both are easy to get using functions. So far I've
had a number of requests for things like this but yours is the first one
that's wanted the name of the makefile currently being parsed, as
opposed to the top level.
nly> How would I submit an RFE?
The URL for the online bug database is available in the GNU make README
file. I also have a link on my site below.
Actually, I notice there's already an RFE for something similar (PR/1446).
--
-------------------------------------------------------------------------------
Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at:
http://www.gnu.org http://www.paulandlesley.org/gmake/
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
