| delorie.com/archives/browse.cgi | search |
| Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
| List-Subscribe: | <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com> |
| List-Archive: | <http://sourceware.cygnus.com/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT sourceware DOT cygnus DOT com> |
| List-Help: | <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs> |
| Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
| Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
| Message-ID: | <C9A8E1D07093D111B76A0000F8C9918A026E1656@zrtpd003.us.nortel.com> |
| From: | "Christopher Jones" <cbjones AT nortelnetworks DOT com> |
| To: | Andre Oliveira da Costa <costa AT cade DOT com DOT br>, 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 14:03:09 -0500 |
| MIME-Version: | 1.0 |
| X-Mailer: | Internet Mail Service (5.5.2448.0) |
------_=_NextPart_001_01BF5DF8.D7BBDBCE Content-Type: text/plain; charset="iso-8859-1" > I'd like to ask for comments on another issue related to > portability from > UNIX --> cygwin, compilation etc.: the way it is now, the linker > automagically appends a .exe suffix to the executable > filename. If you do > > gcc -o foo foo.o > > ld will create foo.exe . > ... > Am I missing something or is this a real problem? 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 ------_=_NextPart_001_01BF5DF8.D7BBDBCE 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 = name (a.exe now)</TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2>> I'd like to ask for comments on another issue = related to </FONT> <BR><FONT SIZE=3D2>> portability from</FONT> <BR><FONT SIZE=3D2>> UNIX --> cygwin, compilation etc.: the way = it is now, the linker</FONT> <BR><FONT SIZE=3D2>> automagically appends a .exe suffix to the = executable </FONT> <BR><FONT SIZE=3D2>> filename. If you do</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> gcc -o foo foo.o</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> ld will create foo.exe .</FONT> <BR><FONT SIZE=3D2>> ...</FONT> <BR><FONT SIZE=3D2>> Am I missing something or is this a real = problem?</FONT> </P> <P><FONT SIZE=3D2>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.</FONT></P> <P><FONT SIZE=3D2>Brian</FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01BF5DF8.D7BBDBCE--
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |