Bug 97737

Summary: Configuration checks in build-webkit need to be updated
Product: WebKit Reporter: Enrica Casucci <enrica>
Component: Tools / TestsAssignee: Enrica Casucci <enrica>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: lforschler, mrowe, simon.fraser
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch mrowe: review-

Enrica Casucci
Reported 2012-09-26 15:59:45 PDT
We need to modernize the checks we perform on the Mac platforms relative to the OS version supported and the minimum Xcode version required. I'm proposing the following: Min OS X version 10.6 (Snow Leopard) with Xcode 3.2 For newer versions of OS X, we should require Xcode 4.2
Attachments
Patch (3.53 KB, patch)
2012-09-26 16:02 PDT, Enrica Casucci 		mrowe: review-
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Enrica Casucci
Comment 1 2012-09-26 16:02:49 PDT
Created attachment 165891 [details] Patch
Simon Fraser (smfr)
Comment 2 2012-09-26 16:07:00 PDT
Dup of bug 90090?
Mark Rowe (bdash)
Comment 3 2012-09-26 16:10:37 PDT
How'd you come up with those version numbers? They seem relatively arbitrary.
Mark Rowe (bdash)
Comment 4 2012-09-26 16:11:25 PDT
*** This bug has been marked as a duplicate of bug 90090 ***
Enrica Casucci
Comment 5 2012-09-26 16:14:33 PDT
(In reply to comment #3) > How'd you come up with those version numbers? They seem relatively arbitrary. I spoke with Lucas, Simon and Anders. I believe 3.2 is the latest Xcode supported on SnowLeopard.
Mark Rowe (bdash)
Comment 6 2012-09-26 16:16:45 PDT
Xcode 4.2 is the last supported version of Xcode on OS X 10.6.
Lucas Forschler
Comment 7 2012-09-26 16:19:27 PDT
chromium folks have SL bots running xcode 3.2.6 If we require > 3.2.6 on SL, this will break them. They appear to be building fine on 3.2.6, so why require 4.2?
Mark Rowe (bdash)
Comment 8 2012-09-26 16:35:48 PDT
What Google does for Chromium isn't relevant to us. We can trivially skip the checks for them.
Note You need to log in before you can comment on or make changes to this bug.