I've been trying to put together a non-recursive build system and ran into
the fact that gmake's "include" directive is always relative to the CWD.
This isn't how cpp does things, and is unexpected behavior to say the least.
Is there some unavoidable reason why relative includes aren't relative to
>
>By the same logic, one can use a (module-specific) variable meaning
>"here" in each sub-directory's make-file fragments; so foo/config.mk
>refers to its source files as $(FOOSRC)/bar.c and so on, rather than
>assuming FOOSRC=. (although that likely remains th
>
> From: Edward Welbourne
>To: Ed H
>Cc: bug-make@gnu.org
>Sent: Wednesday, May 16, 2012 1:21 AM
>Subject: Re: include should be relative to current Makefile
>
>> ifndef TOP
>>
>> include ../Makefile
>>
&
