Many of the utilities used for Windows building are based around Windows XP-era SDK's and VS2005 paths. While many of the build solutions were updated for VS2010, the various command-line tools used by testing bots or other automated environments were not updated to reflect the new tool chain.
This bug makes the following changes:
1. Teach 'webkitdirs.pm' about various acceptable Windows SDK's that users might standardize on to build WebKit.
2. Update 'build-api-tests' to select the correct Visual Studio solution based on the current build environment.
3. Update 'build-dumprendertree' to select the correct Visual Studio solution based on the current build environment.
4. Update 'build-webkit' to select the correct Visual Studio solution based on the current build environment.
Note: The JSC solution needs to also be updated to build as a stand-alone solution. Once that is done, we can update 'build-jsc' to recognize the VS2010 (or newer) environment.
Created attachment 201857 [details]
Created attachment 201858 [details]
Committed r150131: <http://trac.webkit.org/changeset/150131>