This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
RE: [mingw32] Re: [RFC] changing gcc default output executable na me (a.exe now)
- To: <earnie_boyd at yahoo dot com>,<cygwin at sourceware dot cygnus dot com>
- Subject: RE: [mingw32] Re: [RFC] changing gcc default output executable na me (a.exe now)
- From: "Andre Oliveira da Costa" <costa at cade dot com dot br>
- Date: Thu, 13 Jan 2000 18:55:27 -0200
> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Earnie Boyd
> Sent: Thursday, January 13, 2000 6:27 PM
> To: Andre Oliveira da Costa; cygwin@sourceware.cygnus.com
> Subject: RE: [mingw32] Re: [RFC] changing gcc default output executable
> na me (a.exe now)
>
> 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.
It seems like a good (and simple) solution to me. With that, UNIX software
compiled directly from source would compile/install flawlessly if GCC_SUFFIX
is undefined or defined as an empty var. And, the folks who need the .exe
suffix (as stated by Matthew on a message to this thread) could just add
"export GCC_SUFFIX=" to their .bashrc startup files.
Andre
--
André Oliveira da Costa
(costa@cade.com.br)
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com