Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <033b01bf5e07$849766c0$2301a8c0@mediadb.net>
From: "Matthew Brown" <mbrown AT mediadb DOT net>
To: <earnie_boyd AT yahoo DOT com>, "Andre Oliveira da Costa" <costa AT cade DOT com DOT br>,
        <cygwin AT sourceware DOT cygnus DOT com>
References: <20000113202630 DOT 19220 DOT qmail AT web124 DOT yahoomail DOT com>
Subject: Re: [mingw32] Re: [RFC] changing gcc default output executable na me         (a.exe now)
Date: Thu, 13 Jan 2000 15:48:17 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id PAA12001

I could see allowing an option to drop the extension; however, most of us who do cross-platform stuff have customers on Windows who do not use shells at all. For this reason along with that thing about backward-compatibility, I would only want to see it as an option and not the default behavior.

-- Matthew Brown

----- Original Message ----- 
From: "Earnie Boyd" <earnie_boyd AT yahoo DOT com>
To: "Andre Oliveira da Costa" <costa AT cade DOT com DOT br>; <cygwin AT sourceware DOT cygnus DOT com>
Sent: Thursday, January 13, 2000 3:26 PM
Subject: RE: [mingw32] Re: [RFC] changing gcc default output executable na me (a.exe now)


> --- Andre Oliveira da Costa <costa AT cade DOT com DOT br> wrote:
> > Mmmh... ok, I agree this would solve the problem for packages which use
> > autoconf/automake. But those who don't are still in the dark. The worst of
> > it all is that the .exe suffix is added by ld -- it is as if cygwin creates
> > problems for itself...
> > 
> > (before flaming starts: I know there's a very good reason for the insertion
> > of the .exe suffix: it has to be added so that the files can be seen as
> > executables by Windoze -- another great feature (?) by M$oft... =T As I
> > said, I just think it would be nice to have this .exe suffix handled
> > transparently, since it is automagically created)
> > 
> 
> I agree, Andre.  I suggested, years ago now, that the .exe suffix be an
> optional configuration whose default is off.  It isn't needed by the Bourne
> shells we use to execute the programs.  I would like to see this as optional
> with say a GCC_SUFFIX=.exe environment variable.  If GCC_SUFFIX exists it uses
> the value to append to the executable output file.
> 
> 
> =====
> Earnie Boyd <mailto:earnie_boyd AT yahoo DOT com>
> Cygwin Newbies, please visit
> <http://www.freeyellow.com/members5/gw32/index.html>
> __________________________________________________
> Do You Yahoo!?
> Talk to your friends online with Yahoo! Messenger.
> http://im.yahoo.com
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
> 
> 


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com