Mail Archives: cygwin/2000/01/13/15:02:46
------_=_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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2448.0">
<TITLE>RE: [mingw32] Re: [RFC] changing gcc default output executable =
na me (a.exe now)</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>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.</FONT></P>
<P><FONT SIZE=3D2>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.</FONT></P>
<P><FONT SIZE=3D2>Brian</FONT>
</P>
<P><FONT SIZE=3D2>> -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>> From: Andre Oliveira da Costa [<A =
HREF=3D"mailto:costa AT cade DOT com DOT br">mailto:costa AT cade DOT com DOT br</A>]</FONT>
<BR><FONT SIZE=3D2>> Sent: Thursday, January 13, 2000 2:30 PM</FONT>
<BR><FONT SIZE=3D2>> To: cygwin AT sourceware DOT cygnus DOT com</FONT>
<BR><FONT SIZE=3D2>> Subject: RE: [mingw32] Re: [RFC] changing gcc =
default output </FONT>
<BR><FONT SIZE=3D2>> executable</FONT>
<BR><FONT SIZE=3D2>> na me (a.exe now)</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Mmmh... ok, I agree this would solve the =
problem for packages </FONT>
<BR><FONT SIZE=3D2>> which use</FONT>
<BR><FONT SIZE=3D2>> autoconf/automake. But those who don't are =
still in the dark. </FONT>
<BR><FONT SIZE=3D2>> The worst of</FONT>
<BR><FONT SIZE=3D2>> it all is that the .exe suffix is added by ld =
-- it is as if </FONT>
<BR><FONT SIZE=3D2>> cygwin creates</FONT>
<BR><FONT SIZE=3D2>> problems for itself...</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> (before flaming starts: I know there's a very =
good reason for </FONT>
<BR><FONT SIZE=3D2>> the insertion</FONT>
<BR><FONT SIZE=3D2>> of the .exe suffix: it has to be added so that =
the files can </FONT>
<BR><FONT SIZE=3D2>> be seen as</FONT>
<BR><FONT SIZE=3D2>> executables by Windoze -- another great feature =
(?) by </FONT>
<BR><FONT SIZE=3D2>> M$oft... =3DT As I</FONT>
<BR><FONT SIZE=3D2>> said, I just think it would be nice to have =
this .exe suffix handled</FONT>
<BR><FONT SIZE=3D2>> transparently, since it is automagically =
created)</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Regards,</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Andre</FONT>
<BR><FONT SIZE=3D2>> --</FONT>
<BR><FONT SIZE=3D2>> Andr=E9 Oliveira da Costa</FONT>
<BR><FONT SIZE=3D2>> (costa AT cade DOT com DOT br)</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>> From: cygwin-owner AT sourceware DOT cygnus DOT com</FONT>
<BR><FONT SIZE=3D2>> [<A =
HREF=3D"mailto:cygwin-owner AT sourceware DOT cygnus DOT com">mailto:cygwin-owner AT s=
ourceware.cygnus.com</A>]On Behalf Of </FONT>
<BR><FONT SIZE=3D2>> Christopher Jones</FONT>
<BR><FONT SIZE=3D2>> Sent: Thursday, January 13, 2000 5:03 PM</FONT>
<BR><FONT SIZE=3D2>> To: Andre Oliveira da Costa; =
cygwin AT sourceware DOT cygnus DOT com</FONT>
<BR><FONT SIZE=3D2>> Subject: RE: [mingw32] Re: [RFC] changing gcc =
default output </FONT>
<BR><FONT SIZE=3D2>> executable na</FONT>
<BR><FONT SIZE=3D2>> me (a.exe now)</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> I think this should be handled automatically if =
using </FONT>
<BR><FONT SIZE=3D2>> autoconf and automake,</FONT>
<BR><FONT SIZE=3D2>> especially when using automake since the =
install targets for </FONT>
<BR><FONT SIZE=3D2>> executables are</FONT>
<BR><FONT SIZE=3D2>> created by it from bin_PROGS or similar. =
The cygwin stuff in autoconf</FONT>
<BR><FONT SIZE=3D2>> provides a variable which can be checked in =
Makefiles to do something</FONT>
<BR><FONT SIZE=3D2>> specific for a cygwin environment and another =
variable to do something</FONT>
<BR><FONT SIZE=3D2>> cygwin specific in configure.</FONT>
<BR><FONT SIZE=3D2>> Brian</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> --</FONT>
<BR><FONT SIZE=3D2>> Want to unsubscribe from this list?</FONT>
<BR><FONT SIZE=3D2>> Send a message to =
cygwin-unsubscribe AT sourceware DOT cygnus DOT com</FONT>
<BR><FONT SIZE=3D2>> </FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01BF5E01.6B04FB10--
- Raw text -