This is the mail archive of the
mailing list for the Cygwin project.
RE: [mingw32] Re: [RFC] changing gcc default output executable na me (a.exe now)
- To: <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 17:30:03 -0200
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)
André Oliveira da Costa
[mailto:email@example.com]On Behalf Of Christopher Jones
Sent: Thursday, January 13, 2000 5:03 PM
To: Andre Oliveira da Costa; firstname.lastname@example.org
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.
Want to unsubscribe from this list?
Send a message to email@example.com