This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Cygwin compiler and linker options


----- Original Message ----- From: "Warren Young" <warren@etr-usa.com>
Subject: Re: Cygwin compiler and linker options

It's not impossible to have them both in the PATH, but I've come across enough strange behavior that I don't do that anymore.

I posted about how to keep the two separate without making it hard to
switch between them before here:

http://sourceware.org/ml/cygwin/2008-05/msg00092.html

Here's another suggestion....  It won't be terribly helpful for those of you
who prefer 'make' etc but if you need to use multiple compilers and want to
make life simple, this IDE might also be worth considering:-

http://www.codeblocks.org/

Code::Blocks has been specifically designed to accommodate multple compiler
environments.  It comes pre-configured for a variety of popular compilers
including Borland C++, Microsoft Visual C++ (various flavours), GNU GCC,
Watcom, Cygwin GCC, MinGW, Tiny C, Digital Mars etc.

Each project can specify which compiler / debugger it wants to use.  Paths
(include / lib etc) can be specified either globally (as a default for all
compilers) or individually (specific to each compiler) or a combination of
both.  You can also specify whether the project's paths take precedence over
the global paths or vice-versa.  Finally, it's open source and is available
for Linux, Windows and Mac.

John



----- Original Message ----- From: "Warren Young" <warren@etr-usa.com>
To: "Cygwin-L" <cygwin@cygwin.com>
Sent: 22 August 2008 19:52
Subject: Re: Cygwin compiler and linker options



Ralph Hempel wrote:

what I think I hear you saying is that when -mno-cygwin is fully deprecated I'll need to build a cross compiler for native Windows executables

Or, you could install MinGW. Cygwin and MinGW will coexist, side by side, without conflict, if you arrange it so only one is in the PATH at a time. It's not impossible to have them both in the PATH, but I've come across enough strange behavior that I don't do that anymore.

I posted about how to keep the two separate without making it hard to
switch between them before here:

http://sourceware.org/ml/cygwin/2008-05/msg00092.html

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]