Win10/GNUmake4.1: paths in .INCLUDE_DIRS not searched

2016-05-06 Thread Jannick
Hi, '.INCLUDE_DIRS += C:\mypath' does not make GNUmake to look for included makefiles (using 'include') in C:\mypath. I checked that * C:\mypath is added to .INCLUDE_DIRS (with 'make -p') * GNUmake does not look for the includes (with 'make -d') This issue arises when

Re: Win10/GNUmake4.1: paths in .INCLUDE_DIRS not searched

2016-05-06 Thread Eli Zaretskii
> From: "Jannick" > Date: Fri, 6 May 2016 14:25:27 +0200 > > '.INCLUDE_DIRS += C:\mypath' does not make GNUmake to look for included > makefiles (using 'include') in C:\mypath. > > I checked that > > * C:\mypath is added to .INCLUDE_DIRS (with 'make -p') > > * GNUmake does not look

RE: Win10/GNUmake4.1: paths in .INCLUDE_DIRS not searched

2016-05-06 Thread Jannick
Hi Eli, Many thanks for the quick reply! I had a look around in the code and the default include paths are set in read.c (http://git.savannah.gnu.org/cgit/make.git/tree/read.c#n106). Given that I am working on a Windows machine, only the current directory ('.') comes through as default incl

Re: Win10/GNUmake4.1: paths in .INCLUDE_DIRS not searched

2016-05-06 Thread Eli Zaretskii
> From: "Jannick" > Cc: > Date: Sat, 7 May 2016 02:29:05 +0200 > > Would it be possible that the default include path is (1) an environment or > (2) a Make variable? If you want me > to file a feature request somewhere, could you please pass on where to do > that? Before we consider taking th