public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Earnie Boyd <eaboyd@freenet.columbus.oh.us>
To: "AECEULA, QUEST Team" <aecquest@ciens.ula.ve>
Cc: "Andrey A. Kulaga" <kulaga@rp3.menatep.ru>, gnu-win32@cygnus.com
Subject: Re: Default compiler behaviour for b19
Date: Fri, 12 Sep 1997 09:32:00 -0000	[thread overview]
Message-ID: <Pine.3.07.9709121219.A21106-c100000@login> (raw)
In-Reply-To: <3417FCFF.41C67EA6@ciens.ula.ve>

I started looking at gnu-win32 because it was Unix compatible.  Leave the
default the way it is but allow for an environment variable to change the
default behaviour.  That way you can have the best of both worlds.

On Thu, 11 Sep 1997, AECEULA, QUEST Team wrote:

> The idea of generating native win32 binaries by default (i think) is a
> great advance, because you can make your programs to be independient.
> It's true that GCC comes from Unix, but if you can make native win32
> binaries with it, it's a very powerful tool. And i want to have it !
> 
> Andrey A. Kulaga wrote:
> > 
> > It's very important to me to have possibility produce native win32 binaries.
> > It doesn't matter, whether this option will be default. I like GNU tools, but i
> > want my code be portable between compilers. That's why l'm using Minimalist
> > package by Colin Peters (thanks for them).
> > 
> > --------------------
> > > Date: Fri, 05 Sep 1997 11:23:31 +1000
> > > From: Anthony Wesley <awesley@acquerra.com.au>
> > > Reply-To: awesley@mail.acquerra.com.au
> > >
> > > 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@cygnus.com" with one line of text: "help".
> > 
> > -
> > For help on using this list (especially unsubscribing), send a message to
> > "gnu-win32-request@cygnus.com" with one line of text: "help".
> -
> For help on using this list (especially unsubscribing), send a message to
> "gnu-win32-request@cygnus.com" with one line of text: "help".



 \|-----------|/    eaboyd@freenet.columbus.oh.us
--|Earnie Boyd|--       ** text only please **
 /|-----------|\


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

  reply	other threads:[~1997-09-12  9:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-04 21:18 Anthony Wesley
1997-09-09  3:50 ` Geoffrey Noer
1997-09-09 23:33   ` Fergus Henderson
1997-09-11  9:20     ` Christian Soeller
1997-09-09 23:33 ` Andrey A. Kulaga
1997-09-11 10:10   ` AECEULA, QUEST Team
1997-09-12  9:32     ` Earnie Boyd [this message]
1997-09-12 12:07     ` M. Halpin
1997-09-12 20:49       ` Where is b19 Daniyal Syed
1997-09-13 11:51         ` Michael Hirmke
1997-09-09  3:50 Default compiler behaviour for b19 Sonic Junior
1997-09-10 22:54 Colin Peters

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.3.07.9709121219.A21106-c100000@login \
    --to=eaboyd@freenet.columbus.oh.us \
    --cc=aecquest@ciens.ula.ve \
    --cc=gnu-win32@cygnus.com \
    --cc=kulaga@rp3.menatep.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).