On 22 Aug 2011, at 20:26, Matthias Melcher wrote: > > How do I get rid of this one: > > NOTE: WINVER has been defined as 0x0500 or greater which enables > Windows NT 5.0 and Windows 98 features. When these headers were released, > Windows NT 5.0 beta 1 and Windows 98 beta 2.1 were the current versions. > For this release when WINVER is defined as 0x0500 or greater, you can only > build beta or test applications. To build a retail application, > set WINVER to 0x0400 or visit http://www.microsoft.com/msdn/sdk > to see if retail Windows NT 5.0 or Windows 98 headers are available. > See the SDK release notes for more information. > > I did a grep for all obvious values, but I could not find a configuration > setting for it.
Oh yes - I've seen that, but not for a while.... Don't really recall what it means... Um, I think if you stop using VC6 it goes away, but I can't remember... We now use a bunch of API's (e.g. for Unicode etc.) that were added to Windows when VC6 was already old, and I think it just can't cope... Do later compiler tool chains also do it? And whilst I'm on - big check-in there - ouch! Had to massage makeinclude a bit to get it to compile on this Mac; the include path being passed to the compiler had to be extended to: - find config.h and mac_endianness.h (I added -I.. before the -I../include path, 3 places) - none of the image libs could find their headers (I added -I../include/fltk3png -I../include/fltk3jpeg -I../include/fltk3zlib to the .c.o target) Thereafter the build went OK. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
