From: awesley AT acquerra DOT com DOT au (Anthony Wesley)
Subject: Default compiler behaviour for b19
6 Sep 1997 15:11:46 -0700
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <340F5F13.1843.cygnus.gnu-win32@acquerra.com.au>
Reply-To: awesley AT mail DOT acquerra DOT com DOT au
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.01Gold (Win95; I)
Original-To: gnu-win32 AT cygnus DOT com
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Perhaps I am misreading the comments on the gnuwin32 home page, but it
looks like Cygnus are proposing to have "gcc -o foo foo.c" generate
native win32 binaries by default and not link with cygwin.dll. To
compile UNIX-ish tools and link with the cygwin.dll library you will
have to supply an extra command line option.

This seems silly to me, and the wrong way around. After all, gcc and all
the nice tools and development environment came from the UNIX land, so
surely generating UNIX-ish binaries should be the default, making
porting UNIX applications and tools the native mode, whereas generating
pure win32 binaries should be the "foreign" mode.

It would be really strange to have "gcc -o foo foo.c" not work as
expected by people coming from the UNIX world. I realise that this
behavious could be covered up (eg have an environment variable to select
the mode, or put it in the gcc compiler-options file) but I believe that
it would still be the wrong attitude by Cygnus to do this.

Just my AUS $0.0215 worth .. :-)

Anthony
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".