Mail Archives: cygwin/1997/09/12/12:37:53
I think that the default should be to link to cygwin.dll, however
an option should be available for creating independent binaries (I.E. you
can make independent binaries, it's just not default).
Writing the compatibility level would almost be impossible if
programs did not default to cygwin.dll, plus updates would require you to
recompile everything. And that would be a pain in the ...
- SJ
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 AT acquerra DOT com DOT au>
> > > Reply-To: awesley AT mail DOT acquerra DOT com DOT 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 AT cygnus DOT com" with one line of text: "help".
> >
> > -
> > 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".
> -
> 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".
>
-
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".
- Raw text -