VS2003 needs DX9 SDK Version 27, abut VS2010 needs DX9 SDK Version 43 to compile.
By installing both SDKs with unique names, a combined shared StaticSDK area can
be used by Jenkins for a matrix build using both toolchains.
In VS2003 all references to StaticSDKs/Win32/DX9.0c are changed to DX9.0c-V27
In VS2010 all references to StaticSDKs/Win32/DX9.0c are changed to DX9.0c-V43
THIS REQUIRES REARRANGEMENT OF INSTALLED SDKS TO BUILD CWE AND DOC CHANGES
Those who have the EAX SDK should indicate this on the command line by adding /DEAX_SDK_AVAILABLE to environment variable CL.
Trying to keep common project files and configurations between OU and Cyan for now, we'll see how that goes.
MarkD: My thought was for the long term was to put most of the differences in the project and solution configurations, so there would be less differences in the sources. EAX is a good example - I put the #define for EAX_SDK_AVAILABLE in the projects that used it with the thinking that the fans would create new projects that would not have EAX_SDK_AVAILABLE and would create and use a different configuration in the AllClient solution. Cyan would use the "Release" config and the fans use something like "Release-ou" to build with. But maybe there are just too many differences.
Add plClientPatcher and plUruLauncher to AllClient.sln.
Adjust include and library paths in the "Release" build.
Adjust library depedencies to remove EAX, IJL, and Bink, and add IJG jpeg libraries.
Remove some overlooked Havok include files.
Add sample build and clean batch files to build the AllClient solution from a MSVC 2003 command prompt.
rarified
Christian Walther
CyanWorlds
cjkelly1
JWPlatt