This file must be the first file included by all cpp files that are built in any library in the JetByte Tools suite. This file contains global defines that affect how the code is built
This file is included by Admin.h and is used to set the various compilation options that are related to your compile environment. We use a separate header file for this so that it's easy to have multiple copies for different target environments so that the continuous integration build can copy a single file around to change the target environment
This file attempts to automatically detect the Windows SDK version that is installed. Note that it only works if a Windows SDK is actually installed as it requires that sdkddkver.h exists
There are various issues with using various early versions of the platform SDK (or using VC6 and no platform SDK) with the winsock2.h header. This is part of a crude attempt to avoid the problems. It doesn't work very well..
This file provides backwards compatibility macros for the secure CRT functions that Microsoft began supplying starting with VS2005. This allows us to work as if the secure CRT was always available... See here for more details
This file provides some macros that allow pragma JETBYTE_TODO("message") to give a clickable message in the build window from within Visual Studio. Note that all of these messages only show up in debug builds
If you're building with the JetByte Tools libraries and mixing the code with MFC then you may have problems. See here for more details on the likely problems. Including this file is likely to fix those problems as it fixes up the library link order. You only have to include this file once, usually in the 'main()' .cpp file. NOTE THAT YOU MUST INCLUDE THIS FILE BEFORE Admin.h
This file deals with warning level setting and masking of known safe warnings for either STLPort or native Microsoft STL. It's automatically included in all files because they include Admin.h
There are various issues with using various early versions of the platform SDK (or using VC6 and no platform SDK) with the winsock2.h header. This is part of a crude attempt to avoid the problems