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: 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) Date: Thu, 13 Jan 2000 14:03:09 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF5DF8.D7BBDBCE" ------_=_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 RE: [mingw32] Re: [RFC] changing gcc default output executable = name (a.exe now)

> 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--