X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.7 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4B57DF25.4040605@gmail.com>
References: <81D39E818991E549B1F66EB6A7D18422BE8626 AT AVSMOEXCL02 DOT activision DOT com> 	 <4B57DF25 DOT 4040605 AT gmail DOT com>
Date: Fri, 22 Jan 2010 14:17:56 +0100
Message-ID: <7f95d3561001220517k4fd93c6btdda02fd06596e97f@mail.gmail.com>
Subject: Re: Design issue with new MS-DOS style path warning?
From: Eric Vautier <eric.vautier+cygwin AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
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

It may be good advice not to do it.

However, there's the case of environment variables, or parameter files
containing Windows-style paths used in build.xml, for example. It
appears that those variables are not converted sometimes, resulting in
failures.

One of my build files refers to such a property. I get the DOS file
warning at the start of the script, and further down, an error states
that C:/cygdrive/c/Users/... couldn't be found. I wonder how Cygwin
would come to creating such a hybrid path. Did anyone else run into
this? The same script worked perfectly fine before I upgraded to 1.7.
-e



On Thu, Jan 21, 2010 at 5:59 AM, Dave Korn
<dave DOT korn DOT cygwin AT googlemail DOT com> wrote:
> On 21/01/2010 01:11, Batson, Chuck wrote:
>
>> That is, how to avoid the warning in a "clean" way without resorting to
>> the 'nodosfilewarning' option?
>
>> Say, for example, you create a Windows batch file containing the line:
>>
>> =A0 touch C:\foo.txt
>
> =A0Well, don't do that then.
>
> =A0 =A0cheers,
> =A0 =A0 =A0DaveK

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple