----- Original Message -----
From: Theodore Jump <[EMAIL PROTECTED]>
To: Eero Pajarre <[EMAIL PROTECTED]>
Cc: mesa-dev <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, October 20, 1999 1:12 PM
Subject: Re: [Mesa-dev] Major portability problems in latest CVS sources?
>
> I've been building the mesa CVS stuff every couple days (mesa-for-cpu
> rendering, mesa-for-3dfx, glu, glut, and all the samples/demos/book
programs)
> with MSVC 6 SP3. Now, I've only got MSVC set for Warning Level 3, not 4,
> because the code base does generate a large amount of warnings under WL4
> (compilng mesa alone generates over 1000 warnings, I don't know exactly
how
> much because 1000 is the limit for my shell's rollback buffer...).
[snippo]
I've set up an IDE workspace in VC6 SP3, and MesaCVS builds OK. That's only
after I put the damn windows header (windows.h) into Mesa's gl.h file,
though.
What's the story regarding the windows header file? (Brian?) It's alright
editing my own GL code to add it, but it also means altering third-party
code to add "windows.h" to it (imagine adding "#include windows.h" to all of
the Red Book samples - OK you could #if the include, but it still doesn't
feel right). Have I missed something obvious here?...
Regards,
Keith Harrison
SiO2 Software.
Birmingham, UK.
[EMAIL PROTECTED] (personal)
[EMAIL PROTECTED] (work)
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
