X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17610.33952.559618.355180@lemming.engeast.baynetworks.com> Date: Fri, 28 Jul 2006 17:41:52 -0400 To: "John W. Eaton" Cc: bug-make AT gnu DOT org, cygwin AT cygwin DOT com Subject: Re: 3.81 and windows paths In-Reply-To: <17610.11406.472347.801404@segfault.lan> References: <20060727195042 DOT GC27890 AT brasko DOT net> <44C92033 DOT A2978A8E AT dessent DOT net> <17609 DOT 11132 DOT 462789 DOT 443104 AT lemming DOT engeast DOT baynetworks DOT com> <20060727221136 DOT GD6653 AT trixie DOT casa DOT cgf DOT cx> <17610 DOT 6020 DOT 12729 DOT 506044 AT lemming DOT engeast DOT baynetworks DOT com> <17610 DOT 7126 DOT 60597 DOT 468701 AT segfault DOT lan> <17610 DOT 8103 DOT 778129 DOT 918123 AT lemming DOT engeast DOT baynetworks DOT com> <17610 DOT 11406 DOT 472347 DOT 801404 AT segfault DOT lan> X-Mailer: VM 7.19 under Emacs 21.4.1 From: "Paul D. Smith" Reply-To: "Paul D. Smith" Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com %% "John W. Eaton" writes: jwe> 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 jwe> OK, but I still think it should be implemented as an optional jwe> feature that users can select unless we can prove that the jwe> feature doesn't cause trouble for valid Makefiles that use only jwe> Posix filenames. As I said, we can definitely say it could cause trouble, but in pretty rare situations (I believe). Whether that's enough to cause Cygwin to reject this option is, ultimately, up to them. Note I'm not even thinking about making this feature available on non-Windows systems as that just doesn't make sense. | #ifdeffing in GNU make is kind of a mess, with all the different ports | we support. jwe> Yes, that's unfortunate. I don't think that it is necessary to jwe> use an intricate mess of #ifdefs all throughout a program to jwe> achieve portability to a wide variety of systems. That seems to jwe> be a design decision that was made fairly early on in the jwe> development of Make (long before you became the maintainer, I jwe> would guess). Yes, it's too bad. Supporting wildly different host platforms can be done much more cleanly BUT you need to do a lot of up-front work and put a lot of thought into it. Or, you can have something similar to Apache's APR library or whatever available to you. Obviously the GNU make ports weren't handled that way, for quite reasonable reasons. Even so there's a lot of room to clean this up now, but not a lot of incentive I suppose. I asked on some Amiga mailing lists whether that port was still used and useful; if it wasn't I was going to rip it out which would have helped a good bit. But, by gosh, some people actually still do use it! The next version of GNU make will require an ISO 1989 C compiler and runtime library and give up supporting pre-standard K&R compilers. That will help a tiny little bit. -- ------------------------------------------------------------------------------- Paul D. Smith Find some GNU make tips at: http://www.gnu.org http://make.paulandlesley.org "Please remain calm...I may be mad, but I am a professional." --Mad Scientist -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/