RE: [mingw32] Re: [RFC] changing gcc default output executable na me (a.exe now)

["Christopher Jones" <cbjones at nortelnetworks dot com>]

Title: RE: [mingw32] Re: [RFC] changing gcc default output executable na me (a.exe now)

As far as I know the problems which were solved by having the .exe automatically appended to the executable's name could have just as easily been dealt with via Makefiles, and I agree it probably creates more problems than it solves.  For that matter why couldn't we have just been forced to do something like gcc -o a.exe a.c instead?  This interoperability tradeoff has a cost in terms of emulation.

Related to another thread, I think cygwin goes after two slightly different objectives at the same time and it creates problems when you talk about things like the POSIX filenames mentioned earlier.  On the one hand you want to have a UNIX emulation layer and on the other you want to have interoperability with the Windows environment.  I personally place a lot less emphasis on the latter.  Windows be damned.  Maybe there should be two environments, one for compromises to induce interoperability and another without those compromises.  My guess is that the latter would be easier to setup and easier to use.

Brian

> -----Original Message-----
> From: Andre Oliveira da Costa [mailto:costa@cade.com.br]
> Sent: Thursday, January 13, 2000 2:30 PM
> To: cygwin@sourceware.cygnus.com
> Subject: RE: [mingw32] Re: [RFC] changing gcc default output
> executable
> na me (a.exe now)
>
>
> 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
>