delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2000/01/13/00:04:53

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
X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs
Date: Wed, 12 Jan 2000 23:07:40 -0600 (CST)
From: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>
To: Mingw32 discussion list at eGroups <mingw32 AT egroups DOT com>,
cygwin AT sourceware DOT cygnus DOT com
Subject: [RFC] changing gcc default output executable name (a.exe now)
Message-ID: <Pine.HPP.3.96.1000112230321.6294H-100000@hp2.xraylith.wisc.edu>
MIME-Version: 1.0

Are people happy/ok with the fact that gcc on win32 produces a program
called a.exe by default? For example,
  
  $ gcc foo.c

will create a.exe. This is of course not really expected on DOS/Windows
world, and causes all sorts of confusion. Also, this is simply lame even
on Unix, and this historical bit should've disappeared long ago, but
won't since it's a convention now.

I'd like to move to creating <name>.exe, where <name> is the first file
on the list you provided to gcc.
  
  $ gcc foo1.c foo2.c foo3.c

will produce foo1.exe, not a.exe as it does now.

Is this something we should change?? 

Regards,
Mumit



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019