Bug 116169

Summary: [Windows] Update various build scripts for VS2010 (or newer) build environments
Product: WebKit Reporter: Brent Fulgham <bfulgham>
Component: Tools / TestsAssignee: Brent Fulgham <bfulgham>
Status: RESOLVED FIXED    
Severity: Normal CC: bfulgham, commit-queue, dbates
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 116170    
Attachments:
Description Flags
Patch
none
Patch andersca: review+

Brent Fulgham
Reported 2013-05-15 11:10:55 PDT
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.
Attachments
Patch (5.71 KB, patch)
2013-05-15 11:20 PDT, Brent Fulgham 		no flags
DetailsFormatted DiffDiff
Patch (5.67 KB, patch)
2013-05-15 11:28 PDT, Brent Fulgham 		andersca: review+
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Brent Fulgham
Comment 1 2013-05-15 11:20:10 PDT
Created attachment 201857 [details] Patch
Brent Fulgham
Comment 2 2013-05-15 11:28:02 PDT
Created attachment 201858 [details] Patch
Brent Fulgham
Comment 3 2013-05-15 11:36:03 PDT
Committed r150131: <http://trac.webkit.org/changeset/150131>
Note You need to log in before you can comment on or make changes to this bug.