From: anorland@hem2.passagen.se (Anders Norlander) Subject: Re: gcc produces foo.exe, not foo 24 Sep 1998 17:13:58 -0700 Message-ID: <360A0444.EF577C75.cygnus.gnu-win32@hem2.passagen.se> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mumit Khan Cc: gnu-win32@cygnus.com Mumit Khan wrote: > > On Wed, 23 Sep 1998, Arne Glenstrup wrote: > > > > > The problem is that it seems that when running > > > > gcc -o foo foo.c > > > > it produces not a file named foo, but a file named foo.exe. This has > > caused me problems when writing a Makefile somewhat like > > > > bar: foo.c > > gcc -o foo foo.c > > mv foo bar > > > > because it complains when trying to mv file foo. > > > > What is the standard way of circumventing this problem? Simply writing > > > > mv foo.exe bar.exe > > > > All my local configuration systems check for executable extension and > define a variable such as exeext to either the extension or "" if none > is added by default. Lots of GNU Makefiles are beginning to use this > as well. The Makefile rules look like the following: > > PROGRAMS = bar$(exeext) > > bar$(exeext): foo.c > $(CC) -o foo foo.c > mv foo$(exeext) bar$(exeext) > > Rather ugly, but currently the only usable solution. > > As for the rationale for adding the automatic .exe, I'm somewhat in > favor of, if not thrilled by, such "native compliance"; for mingw32, it > makes perfect sense (must have .exe to jive with native system and also > be executable by native shell); for cygwin32, bash can run programs > with or without .exe, but have trouble when running with native shell. Just an interesting fact. Executables can actually have any extension *except* "" in win32. The limitation of the ".exe" extension is not built in the kernel, but in the shell, i.e it is possible to start processes with any extension via `CreateProcess' but not with ShellExecute (which instead tries to find an associated program). /Anders - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".