> Date: Tue, 8 Jul 2014 13:55:40 +0100
> From: Jonny Grant
> Cc: psm...@gnu.org, bug-make@gnu.org
>
> On 8 July 2014 03:38, Eli Zaretskii wrote:
> >> From: Paul Smith
> >> Cc: Eli Zaretskii , bug-make@gnu.org
> >> Date: Mon, 07 Jul 2014 17:00:03 -0400
> >>
> >> I do wonder, though, why we have
On 8 July 2014 03:38, Eli Zaretskii wrote:
>> From: Paul Smith
>> Cc: Eli Zaretskii , bug-make@gnu.org
>> Date: Mon, 07 Jul 2014 17:00:03 -0400
>>
>> I do wonder, though, why we have both "makefile" and "Makefile" above.
>> Does that actually ever do anything on Windows, other than waste a bit
>>
> From: Paul Smith
> Cc: Eli Zaretskii , bug-make@gnu.org
> Date: Mon, 07 Jul 2014 17:00:03 -0400
>
> I do wonder, though, why we have both "makefile" and "Makefile" above.
> Does that actually ever do anything on Windows, other than waste a bit
> of time checking for the same file twice?
No.
_
I believe it's theoretically possible to have a case-sensitive
filesystem on Windows though it would primarily benefit masochists.
On Mon, Jul 7, 2014 at 5:00 PM, Paul Smith wrote:
> On Mon, 2014-07-07 at 21:15 +0100, Jonny Grant wrote:
>> +#ifdef WINDOWS32
>> + { "GNUmakefile", "makefile", "Make
On Mon, 2014-07-07 at 21:15 +0100, Jonny Grant wrote:
> +#ifdef WINDOWS32
> + { "GNUmakefile", "makefile", "Makefile", "makefile.mak", 0 };
> +#else
This is OK with me. I definitely don't want to add "Makefile.mk" to the
UNIX/POSIX side; that's not something anyone ever uses anyway.
I do wonder,
On 7 July 2014 07:06, Paul Smith wrote:
> On Mon, 2014-06-30 at 21:28 +0100, Jonny Grant wrote:
>> I have a few, but triggered by make -f makefile.mak. So it would be
>> quite useful GNU Make could pick up the Windows makefile extension
>> .MAK
>
> If Eli feels this is useful for Windows implement
> Date: Mon, 7 Jul 2014 17:42:18 +0200
> From: Norbert Thiebaud
> Cc: psm...@gnu.org, j...@jguk.org, "bug-make@gnu.org"
>
> >> Renaming the Windows README files is also fine with me if it's fine with
> >> Eli.
> >
> > My only doubt about this request is that README files for other
> > platforms
On Mon, Jul 7, 2014 at 4:59 PM, Eli Zaretskii wrote:
>> From: Paul Smith
>> Cc: Eli Zaretskii , bug-make@gnu.org
>> Date: Mon, 07 Jul 2014 02:06:54 -0400
>>
>> On Mon, 2014-06-30 at 21:28 +0100, Jonny Grant wrote:
>> > I have a few, but triggered by make -f makefile.mak. So it would be
>> > quite
> From: Paul Smith
> Cc: Eli Zaretskii , bug-make@gnu.org
> Date: Mon, 07 Jul 2014 02:06:54 -0400
>
> On Mon, 2014-06-30 at 21:28 +0100, Jonny Grant wrote:
> > I have a few, but triggered by make -f makefile.mak. So it would be
> > quite useful GNU Make could pick up the Windows makefile extensio
On Mon, 2014-06-30 at 21:28 +0100, Jonny Grant wrote:
> I have a few, but triggered by make -f makefile.mak. So it would be
> quite useful GNU Make could pick up the Windows makefile extension
> .MAK
If Eli feels this is useful for Windows implementations he can add it;
however, I don't want this
On Mon Jun 30 21:28:43 2014, j...@jguk.org (Jonny Grant) wrote:
> Hi Eli
>
> I have a few, but triggered by make -f makefile.mak. So it would be
> quite useful GNU Make could pick up the Windows makefile extension
> .MAK
On non-Windows platforms I've seen .mk quite a few times,
but never .mak.
>
Hi Eli
I have a few, but triggered by make -f makefile.mak. So it would be
quite useful GNU Make could pick up the Windows makefile extension
.MAK
I would also rename README.W32 to be README_W32.txt
Regards, Jon
On 28 June 2014 15:11, Eli Zaretskii wrote:
>> Date: Sat, 28 Jun 2014 12:12:32 +
> Date: Sat, 28 Jun 2014 12:12:32 +0100
> From: Jonny Grant
>
> Rationale, on Windows makefiles often have this name for other "make"
> programs. In addition it is easier to associate with an editor because
> it has an extension.
FWIW, I have only one makefile.mak on my system, and it seems to b
13 matches
Mail list logo
