Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sourceware.cygnus.com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin@sourceware.cygnus.com>
List-Help: <mailto:cygwin-help@sourceware.cygnus.com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner@sourceware.cygnus.com
Delivered-To: mailing list cygwin@sourceware.cygnus.com
From: "Andre Oliveira da Costa" <costa@cade.com.br>
To: <cygwin@sourceware.cygnus.com>
Subject: RE: [mingw32] Re: [RFC] changing gcc default output executable na me         (a.exe now)
Date: Thu, 13 Jan 2000 17:30:03 -0200
Message-ID: <002a01bf5dfc$97121670$8400000a@costa.cadenet.com.br>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Importance: Normal
In-Reply-To: <C9A8E1D07093D111B76A0000F8C9918A026E1656@zrtpd003.us.nortel.com>

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)

Regards,

Andre
--
André Oliveira da Costa
(costa@cade.com.br)

-----Original Message-----
From: cygwin-owner@sourceware.cygnus.com
[mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Christopher Jones
Sent: Thursday, January 13, 2000 5:03 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 think this should be handled automatically if using autoconf and automake,
especially when using automake since the install targets for executables are
created by it from bin_PROGS or similar.  The cygwin stuff in autoconf
provides a variable which can be checked in Makefiles to do something
specific for a cygwin environment and another variable to do something
cygwin specific in configure.
Brian


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

