Re: gcc-nocygwin-tools

From: Raoul Gough (raoulgough_at_[hidden])
Date: 2002-05-11 05:00:54

----- Original Message -----
From: "David Abrahams" <david.abrahams_at_[hidden]>
To: <jamboost_at_[hidden]>; <RaoulGough_at_[hidden]>
Sent: Friday, May 10, 2002 12:05 PM

> 1. It seems to me that since we can all get ahold of mingw 2.95.x, the
> great advantage of this toolset would be to be able to use gcc-3.0.x in
> nocygwin mode.

It saves me having two compilers installed. I like using cygwin because
there are heaps of tools already available, and unixy things port to it
pretty easily. The fact that the same compiler can also produce windows
binaries is a real bonus.

> However, if I use gcc-mingw.mak with "CXX=g++ -mno-cygwin"
> to build STLPort, I get reams of errors.

I remember having to mess around to get this to work, but ultimately came up
with the following, which works on my cygwin installation at least:

CXXFLAGS_COMMON
= -mno-cygwin -mthreads -fvtable-thunks -I/usr/include/mingw -I${STLPORT_DIR
} ${WARNING_FLAGS}

I don't now remember specifically why I added -I/usr/include/mingw. It seems
redundant with -mno-cygwin option, but I think this made the errors go away.
Obviously -mthreads and -fvtable-thunks are optional.

>
> 2. Was there a reason to use NOCYGWIN_THUNKS as opposed to making a
> feature?
>
> feature vtbl-layout : special platform

Certainly no good reason :-) I took the easy option, because I didn't really
understand how to select features for a build (I see from your other post
how to do it). This could be a useful feature for use with the mingw
compiler as well. I guess you're all pretty busy with the 1_28 release, so
I'll have a go at adding the feature tomorrow .

Regards,
Raoul Gough.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com