content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: RE: exe handling
Date: Wed, 19 Jul 2006 14:10:44 +0100
Message-ID: <6A5097DB1E5EF64AA1AFBE6736133627C9D448@harexch.win.ansys.com>
From: "Oliver Walsh" <Oliver.Walsh@ansys.com>
To: <cygwin@cygwin.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

> -----Original Message-----
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On
Behalf
> Of Corinna Vinschen
> Sent: 19 July 2006 13:51
> To: cygwin@cygwin.com
> Subject: Re: exe handling
> 
> On Jul 19 13:41, Oliver Walsh wrote:
> > > From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On
> 
> http://cygwin.com/acronyms/#PCYMTNQREAIYR
> 
> > > The general idea for the future is to avoid having a file "foo"
and a
> > > file "foo.exe" in the same directory like pestilence.
> >
> > Ok, I can't avoid having both files in the same location but I can
just
> > call foo.exe from foo when run from cygwin.
> 
> Can't you put the unix wrapper scripts (or whatever they are) into
> another path which has precedence over the Cygwin bin path in $PATH?

Yea I could to that, but I'd rather keep the scripts and makefiles as
generic as possible. There are already enough exceptions for windows. 

Thanks,
Ollie


--
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/