This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Default compiler behaviour
- To: gnu-win32 at cygnus dot com
- Subject: Default compiler behaviour
- From: Gunther Ebert <gunther dot ebert at ixos-leipzig dot de>
- Date: Fri, 12 Sep 1997 07:31:27 +0200
- Organization: iXOS Anwendungs-Software GmbH
Hi,
I don't understand this discussion at all. Actually, from the
OS' point of view, it doesn't matter which library is linked
in a program (either crtdll.dll or cygwin.dll), the program
is considered to be 'native Win32' in both cases (you don't need
another subsystem in order to run cygwin programs, do you?).
Which library should gcc link in per default?
Currently I have installed both the original b18 package and
the mingw32 package on my system. Each is installed in a
separate path, between which I can switch using the GCC_EXEC_PREFIX
environment variable:
..\
|
|---cygnus\
|
|----H-i386-cygwin32\<cygwin specific stuff>
|
|----H-i386-mingw32\<mingw32 specific stuff>
|
|----include\
| |
| |----g++\
|
|----windows32sdk\.....
Common parts like the Windows32 SDK or the C++ header files are
installed in another path which does not depend on the GCC_EXEC_PREFIX
setting. This installation works smoothly for me. The default
compiler behaviour depends just on the initial setting of the
GCC_EXEC_PREFIX environment variable, so you are free to choose
your favorite one.
Just an opinion,
Gunther
--
Gunther Ebert
iXOS Anwendungs-Software GmbH
Angerstrasse 40-42
D-04177 Leipzig
Phone : +49 341 48503-0
Fax : +49 341 48503-99
E-mail: mailto:gunther.ebert@ixos-leipzig.de
www : http://www.ixos-leipzig.de
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".