www.delorie.com/archives/browse.cgi | search |
X-Spam-Check-By: | sourceware.org |
MIME-Version: | 1.0 |
Message-ID: | <17609.11894.362091.111863@lemming.engeast.baynetworks.com> |
Date: | Thu, 27 Jul 2006 17:21:58 -0400 |
To: | Brian Dessent <brian AT dessent DOT net>, cygwin AT cygwin DOT com, bug-make AT gnu DOT org |
Subject: | Re: 3.81 and windows paths |
In-Reply-To: | <17609.11132.462789.443104@lemming.engeast.baynetworks.com> |
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> |
X-Mailer: | VM 7.19 under Emacs 21.4.1 |
From: | "Paul D. Smith" <psmith AT gnu DOT org> |
Reply-To: | "Paul D. Smith" <psmith AT gnu DOT org> |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
%% I wrote: pds> I believe that this support is limited to handling drive letters without pds> choking on the ":", actually: IIRC the native support still requires pds> forward slashes (/) rather than backslashes (\). I could be wrong pds> though. I'm not sure how Cygwin's pathname management patches worked. pds> In fact, I'm wondering if there is an advantage to building GNU make pds> using the Cygwin environment, vs. using a native MingW (for example) pds> build of GNU make? I'm afraid I'm woefully ignorant about the details. Now that I think about this more... There is a separate #define use to enable/disable special handling of DOS pathnames in vanilla GNU make: HAVE_DOS_PATHS This feature is not controlled by the generic WINDOWS32 #define. I don't see any reason, offhand, that HAVE_DOS_PATHS couldn't be set in the Cygwin build of GNU make, even though that build is otherwise using standard POSIX and not the Windows system API. In theory that would very easily allow the Cygwin build of GNU make to continue to be a Cygwin application, but with added support for DOS pathnames similar to what you get if you build for native Windows. Of course I've never tried this combination so there may be more to it (it may use some special functions under the w32 directory, and/or there may be some incorrectly #ifdef'd sections of code that need to be fixed). But, it might be worth pursuing. -- ------------------------------------------------------------------------------- Paul D. Smith <psmith AT gnu DOT org> 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |