Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: From: "Christopher Jones" To: cygwin AT sourceware DOT cygnus DOT com Subject: RE: [mingw32] Re: [RFC] changing gcc default output executable na me (a.exe now) Date: Thu, 13 Jan 2000 15:04:36 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF5E01.6B04FB10" ------_=_NextPart_001_01BF5E01.6B04FB10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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 AT cade DOT com DOT br] > Sent: Thursday, January 13, 2000 2:30 PM > To: cygwin AT sourceware DOT cygnus DOT com > Subject: RE: [mingw32] Re: [RFC] changing gcc default output=20 > executable > na me (a.exe now) >=20 >=20 > Mmmh... ok, I agree this would solve the problem for packages=20 > which use > autoconf/automake. But those who don't are still in the dark.=20 > The worst of > it all is that the .exe suffix is added by ld -- it is as if=20 > cygwin creates > problems for itself... >=20 > (before flaming starts: I know there's a very good reason for=20 > the insertion > of the .exe suffix: it has to be added so that the files can=20 > be seen as > executables by Windoze -- another great feature (?) by=20 > M$oft... =3DT As I > said, I just think it would be nice to have this .exe suffix handled > transparently, since it is automagically created) >=20 > Regards, >=20 > Andre > -- > Andr=E9 Oliveira da Costa > (costa AT cade DOT com DOT br) >=20 > -----Original Message----- > From: cygwin-owner AT sourceware DOT cygnus DOT com > [mailto:cygwin-owner AT sourceware DOT cygnus DOT com]On Behalf Of=20 > Christopher Jones > Sent: Thursday, January 13, 2000 5:03 PM > To: Andre Oliveira da Costa; cygwin AT sourceware DOT cygnus DOT com > Subject: RE: [mingw32] Re: [RFC] changing gcc default output=20 > executable na > me (a.exe now) >=20 > I think this should be handled automatically if using=20 > autoconf and automake, > especially when using automake since the install targets for=20 > 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 >=20 >=20 > -- > Want to unsubscribe from this list? > Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com >=20 ------_=_NextPart_001_01BF5E01.6B04FB10 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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 AT cade DOT com DOT br]
> Sent: Thursday, January 13, 2000 2:30 PM
> To: cygwin AT sourceware DOT cygnus DOT 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... =3DT 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=E9 Oliveira da Costa
> (costa AT cade DOT com DOT br)
>
> -----Original Message-----
> From: cygwin-owner AT sourceware DOT cygnus DOT com
> [mailto:cygwin-owner AT s= ourceware.cygnus.com]On Behalf Of
> Christopher Jones
> Sent: Thursday, January 13, 2000 5:03 PM
> To: Andre Oliveira da Costa; = cygwin AT sourceware DOT cygnus DOT 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 AT sourceware DOT cygnus DOT com
>

------_=_NextPart_001_01BF5E01.6B04FB10--