X-Spam-Check-By: sourceware.org Message-ID: <44C940D2.3E07ABCA@dessent.net> Date: Thu, 27 Jul 2006 15:40:18 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: 3.81 and windows paths References: <008e01c6b1cc$76021310$280aa8c0 AT oius DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 William Sheehan wrote: > I can imagine that the immediate response to this complaint will be "fix > your Makefiles to work with Cygwin if it's such an important component." As > others have mentioned, this is no simple task in very large Makefile systems > that support a wide variety of compilation toolchains. Cygwin make has > supported Win32 paths for a long time, so much that I would say that people > have come to rely on it. I am not saying that the changes are impossible; > just that it is a larger inconvenience than some may realize. In that case, spend your time working with the Make developers to get a patch accepted upstream that enables Windows path handling in Cygwin builds, so that there is not a large and cumbersome out-of-tree patch that has to be ported to each new make release. Remember this is a volunteer effort, and SHTDI. Or you can stick with make 3.80. Brian -- 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/