This is the mail archive of the cygwin-apps 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: gcc4: next release (Dave Korn we need you)


On Jul 12 05:25, Yaakov S wrote:
> On Mon, 2010-07-12 at 10:41 +0200, Corinna Vinschen wrote:
> > You're missing number 4.  Cygwin and Mingw are targeting the same
> > underlying "real" target, which is Windows.  Both systems use different
> > approaches and both have their own set of libs and headers which only
> > make sense in their own environment.  But underneath they both run on
> > Windows.  For that reason my POV is that w32api is an intrinsic part of
> > the system and that's why it belongs into /usr/include and /usr/lib.
> > IMHO.
> 
> OTOH there are a number of packages out there that see <windows.h> in
> the default include path and say, "Oh, this must be a Windows system!
> Let's use winsock/GDI/etc."  which is often -- but not always --
> incorrect on Cygwin.  w32api may not be limited to cross-compiling, but
> having it in the default search path isn't always great either.

Yeah, everything comes with a price tag.

> > As for the path issue, I'd prefer to get a layout which closely
> > resembles the Fedora mingw filesystem layout as in
> > http://fedoraproject.org/wiki/Packaging/MinGW#Filesystem_layout.
> 
> That is what I'm working with now.

Nice.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat


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