Re: [Mingw-users] mingw32-make

[Keith M. <kei...@us...>]

On Sunday 22 March 2009 15:34:52 Thomas D. Dean wrote:
> Gnu Make has a list of directories built-in that are searched for
> include files.  GNU Make does search /usr/local/include for
> included files.

So, if that's the only one which is searched, (although I assume the 
current working directory is too), then couldn't you just use it?  
However, it does seem like an odd choice, since I'd normally expect 
this directory to be populated exclusively by C/C++ header files.

I don't often use make's include facility, (other than for generated 
dependency rules, which are normally written in cwd anyway).  When I 
have used it in the past, for a common rule set, for a collection of 
similar, but only superficially related projects, I set it up thus:

  make-includes = ../common/
  include $(make-includes)defaults.mak

which gives a default location relative to the parent of each of the 
individual project directories, but still allows me to override it, 
for any individual project, on the command line, with:

  make make-includes=/path/for/includes/ ...

In general, my preference would be to avoid relying on *any* built-in 
path for Makefile includes, especially when that appears to collide 
with a location I'd normally reserve for a different type of file.

Beyond that, if you have further issues with this, I'd suggest that 
you refer them directly to the GNU make maintainers, via their w32 
specific list, mailto:mak...@gn...

-- 

Regards,
Keith.