[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 3.81 and windows paths
From: |
John W. Eaton |
Subject: |
Re: 3.81 and windows paths |
Date: |
Fri, 28 Jul 2006 11:26:06 -0400 |
On 28-Jul-2006, Paul D. Smith wrote:
| This would be very tricky: right now all the code to do DOS vs. POSIX
| pathnames is controlled through #ifdefs, so it's a compile-time thing.
| Changing it to a runtime thing would be a lot of work, I think... the
OK, but I still think it should be implemented as an optional feature
that users can select unless we can prove that the feature doesn't
cause trouble for valid Makefiles that use only Posix filenames.
| #ifdeffing in GNU make is kind of a mess, with all the different ports
| we support.
Yes, that's unfortunate. I don't think that it is necessary to use an
intricate mess of #ifdefs all throughout a program to achieve
portability to a wide variety of systems. That seems to be a design
decision that was made fairly early on in the development of Make
(long before you became the maintainer, I would guess).
jwe
- Re: 3.81 and windows paths, (continued)
- Re: 3.81 and windows paths, Paul D. Smith, 2006/07/28
- Re: 3.81 and windows paths, Christopher Faylor, 2006/07/28
- Re: 3.81 and windows paths, Paul D. Smith, 2006/07/28
- Re: 3.81 and windows paths, Eli Zaretskii, 2006/07/29
- Re: 3.81 and windows paths, John W. Eaton, 2006/07/28
- Re: 3.81 and windows paths, Paul D. Smith, 2006/07/28
- Re: 3.81 and windows paths, Chris Taylor, 2006/07/28
- Re: 3.81 and windows paths, John W. Eaton, 2006/07/28
- Re: 3.81 and windows paths,
John W. Eaton <=
- Re: 3.81 and windows paths, Paul D. Smith, 2006/07/28
Re: 3.81 and windows paths, Jon Grant, 2006/07/27