Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Message-ID: <033401bf5e06$386b6400$2301a8c0@mediadb.net> From: "Matthew Brown" To: , References: <20000113203131.29351.qmail@web116.yahoomail.com> Subject: Re: [mingw32] Re: [RFC] changing gcc default output executable name (a.exe now) Date: Thu, 13 Jan 2000 15:38:59 -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 PAA11522 But, of course. Just define EXEEXT to be empty. This is how it works on UNIX flavors. -- Matthew Brown ----- Original Message ----- From: "Earnie Boyd" To: "Matthew Brown" ; Sent: Thursday, January 13, 2000 3:31 PM Subject: Re: [mingw32] Re: [RFC] changing gcc default output executable name (a.exe now) > Matthew, > > Your process would still work if gcc didn't append the .exe to the executable > name. You would just do gcc -o myprog$(EXEEXT) instead of gcc -o myprog. > > Earnie. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com