Status

defect
RESOLVED FIXED
13 years ago
13 years ago

People

(Reporter: mark, Assigned: mark)

Tracking

({fixed1.8.1.1})

Details

Attachments

(1 attachment)

Assignee

Description

13 years ago
 
Assignee

Comment 1

13 years ago
Posted patch Do itSplinter Review
Attachment #244460 - Flags: review?(mikepinkerton)
Assignee

Comment 2

13 years ago
I'll also need to set the SDK manually on the 10.3 builders to 10.3.0, and tweak the mozconfig on maya as well to avoid having the universal mozconfig override the ppc SDK setting back to 10.2.8.
Comment on attachment 244460 [details] [diff] [review]
Do it

Since Xcode 2.x is using the SDKROOT_ppc part, can't you just set the vanilla SDKROOT to the 10.3.0 SDK and save yourself a step when making Xcode 1.5/pawn et al. happy?

Or does that get mangled when upgrading the project in Xcode 2?
Assignee

Comment 4

13 years ago
Doesn't really save a step - pawn and friends build via a "make" invocation of "xcodebuild," using the SDK from the mozconfig.  It might make things a little bit easier to build in a 10.3 development environment (which should be deprecated, dammit!) so I can check this in with SDKROOT = 10.3.0.
Comment on attachment 244460 [details] [diff] [review]
Do it

r/sr=pink

make it so
Attachment #244460 - Flags: review?(mikepinkerton) → review+
Assignee

Comment 6

13 years ago
In - will follow up for 1.8 branch after it's proven on the trunk.
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED
On Xcode 2.x on PPC, after upgrading a new project, all the targets point to the 10.3.0 SDK (which causes build errors, since it doesn't exist).
Assignee

Comment 8

13 years ago
Yes.  We need to fix this.
Assignee

Comment 9

13 years ago
I changed it so that there's only a single SDKROOT (10.3.9) and MACOSX_DEPLOYMENT_TARGET (10.3).

Updated

13 years ago
Blocks: 300304
Assignee

Updated

13 years ago
Keywords: fixed1.8.1.1
You need to log in before you can comment on or make changes to this bug.