X-Spam-Check-By: sourceware.org Date: Fri, 28 Jul 2006 13:00:47 +0300 Message-Id: From: Eli Zaretskii To: "Paul D. Smith" CC: brian AT dessent DOT net, cygwin AT cygwin DOT com, bug-make AT gnu DOT org In-reply-to: <17609.11132.462789.443104@lemming.engeast.baynetworks.com> (psmith@gnu.org) Subject: Re: 3.81 and windows paths Reply-to: Eli Zaretskii 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> 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 > Date: Thu, 27 Jul 2006 17:09:16 -0400 > From: "Paul D. Smith" > Cc: cygwin AT cygwin DOT com, bug-make AT gnu DOT org > > I believe that this support is limited to handling drive letters without > choking on the ":", actually: IIRC the native support still requires > forward slashes (/) rather than backslashes (\). I could be wrong > though. It is indeed safer to use forward slashes throughout in the native Windows port, but backslashes are supported in most places in the Makefile, in particular in rule's commands. -- 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/