StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>As things have moved on since the original post on 3by9.com, here are the steps that I had to follow to get the environment working on my PowerBook G4.</p> <p><strong>BTW, I would like to say that I realise that this is not a supported environment and I share this for purely pedagogic rea</strong>sons.</p> <ol> <li>Download and install the iPhoneSDK (final version)</li> <li>After the install finishes, navigate to the packages directory in the mounted DMG</li> <li>Install all of the pkg's that start with iPhone</li> <li>Copy the contents of <code>/Platforms</code> to <code>/Developer/Platforms</code> (should be two folders starting with iPhone)</li> <li>Locate '<code>iPhone Simulator Architectures.xcspec</code>' in <code>/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Xcode/Specifications</code> and open in a text editor.</li> <li>Change line 12 to: <code>Name = "Standard (iPhone Simulator: i386 ppc)";</code></li> <li>Change line 16 to: <code>RealArchitectures = ( i386, ppc );</code></li> <li>Add the following to line 40 onwards:</li> </ol> <pre> // PowerPC { Type = Architecture; Identifier = ppc; Name = "PowerPC"; Description = "32-bit PowerPC"; PerArchBuildSettingName = "PowerPC"; ByteOrder = big; ListInEnum = NO; SortNumber = 106; }, </pre> <ol start="9"> <li>Save the file and start Xcode</li> <li>You should see under the New Project Folder the ability to create iPhone applications.</li> <li>To get an app to work in the simulator (and using the WhichWayIsUp example) open Edit Project Settings under the Project menu</li> <li>On the Build tab change the Architectures to: Standard (iPhone Simulator:i386 ppc)</li> <li>Change Base SDK to Simulator - iPhone OS 2.0</li> <li>Build and go should now see the app build and run in the simulator</li> </ol>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload