This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: gcc produces foo.exe, not foo
- To: gnu-win32 at cygnus dot com
- Subject: Re: gcc produces foo.exe, not foo
- From: Arne Glenstrup <panic at diku dot dk>
- Date: Thu, 24 Sep 1998 11:17:20 +0200 (METDST)
- Reply-To: Arne Glenstrup <panic at diku dot dk>
Now that we have established that we need some (in my opinion) dirty
$(EXEEXT)-stuff, what is the consensus on how to use it with regards to
makefile targets and -o switches to compilers? Should a makefile look
like this:
EXEEXT = @EXEEXT@
goal$(EXEEXT): goal.c
$(CC) -o goal$(EXEEXT) goal.c
cp goal$(EXEEXT) anothergoal$(EXEEXT)
mv goal$(EXEEXT) yet.another.goal
or should it look like this:
EXEEXT = @EXEEXT@
goal: goal.c
$(CC) -o goal goal.c
cp goal$(EXEEXT) anothergoal$(EXEEXT)
mv goal$(EXEEXT) yet.another.goal
-- Arne
__________________________________________________________________________
Arne John Glenstrup | Windows 95: n. 32 bit extensions and a
panic@diku.dk | graphical shell for a 16 bit patch to an 8
http://www.diku.dk/~panic/ | bit operating system originally coded for a 4
bit microprocessor, written by a 2 bit company
that can't stand 1 bit of competition.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".