From: Danny S. <dan...@cl...> - 2003-03-12 20:54:12
|
----- Original Message ----- From: "Christopher Faylor" <cg...@re...> To: <min...@li...> Sent: Wednesday, 12 March 2003 19:42 Subject: Re: [MinGW-dvlpr] GCC cygming > Danny, > I don't know if you saw the discussion in cygwin at cygwin wrt how awful > it is that we have nifty stuff on the gcc branch that hasn't made it into > the trunk, but I was wondering how close you are to releasing this > work. I'm running the testsuites now. One alterartion since last update: Using environ var as switch to convet to mingw include paths can cause problems for the clever user who does: export GCC_CYGWIN_MINGW=1 gcc foo.c will cause conversion to mingw include paths, but rest of specs are still -mcygwin so I.ve put a putenv ("GCC_CYGWIN_MINGW=0"); as the first thing mingw_scan does The only way to get -mno-cygwin is with -mno-cygwin. Danny > > If you have something that's close and don't have the time to get around > to finishing off, I wouldn't mind picking up the ball. I *may* have some > time this weekend. I think I'll be stuck in a hotel room with nothing else > to do. > > cgf > > On Fri, Mar 07, 2003 at 10:02:41PM -0500, Christopher Faylor wrote: > >On Wed, Mar 05, 2003 at 09:46:25AM +0000, Danny Smith wrote: > >>All this may be OT for mingw-dvlprs. If that is general opinion, I'll > >>move off-list, but I think the distinction of runtime headers and w32api > >>headers may have relevance to "native" mingw too. > >> > >> > >>This message > >> > >>http://sources.redhat.com/ml/cygwin/2003-03/msg00271.html > >> > >>wanted the include/w32api dir to have priority over all other C include > >>dirs with -mwin32 switch. Is there value in that? Currently all mwin32 > >>does is add the -D_WIN32 series of defines for cygwin. > > > >I don't think there is any value in doing this, no. Changing .../w32api > >into a -idirafter rather than a -isystem is correct though. That was > >a thinko on my part, I think. Either that or I had a great reason for > >doing that and I forgot it. > > > >>Note that, for -mno-cygwin there is _no_ > >>/usr/i686-pc-mingw32/include/w32api > > > >I don't think there should be. > > > >>I'll start experimenting with .pch now to see how it interact with all > >>this, before submitting anything. In longer term, it may be of value > >>for mingw to separate out the w32api headers too, to make it easier to > >>manage precompiled headers. > > > >It would be nice if cygwin and mingw did it the same way but separating > >the headers isn't how Microsoft does it. Not that that matters, I guess. > > > >cgf > > > > > >------------------------------------------------------- > >This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger > >for complex code. Debugging C/C++ programs can leave you feeling lost and > >disoriented. TotalView can help you find your way. Available on major UNIX > >and Linux platforms. Try it free. www.etnus.com > >_______________________________________________ > >MinGW-dvlpr mailing list > >Min...@li... > >https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr > > > ------------------------------------------------------- > This SF.net email is sponsored by:Crypto Challenge is now open! > Get cracking and register here for some mind boggling fun and > the chance of winning an Apple iPod: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr |