Building iTGB 1.2 on Snow Leopard
by Gregg Patton · in iTorque 2D · 09/06/2009 (1:11 pm) · 8 replies
I noticed after I upgraded to Snow Leopard that building for iPhone OS 2.2.1 is no longer an option. You also have to upgrade XCode and the iPhone SDK when you upgrade to Snow Leopard.
It seems that upgrading to Snow Leopard before the iTGB 1.3 release will be problematic for building iTGB apps.
Just wanted to mention it in case someone wasn't aware of it.
It seems that upgrading to Snow Leopard before the iTGB 1.3 release will be problematic for building iTGB apps.
Just wanted to mention it in case someone wasn't aware of it.
#2
Somebody please hurry up and release 1.3 so we can at least *compile* on Snow Leopard without having to spend hours hacking!
09/06/2009 (6:16 pm)
I've built with GCC 4.2 at some point, but the fix for that should be in the very delayed 1.3 release of the engine ;)Somebody please hurry up and release 1.3 so we can at least *compile* on Snow Leopard without having to spend hours hacking!
#3
But yea I did hack for about 30 minutes to get it to compile on GCC 4.2 a few months ago when 1.2 first came out.
09/06/2009 (9:39 pm)
I've compiled on GCC 4.2 on snow leopard and it ran fine on my iPhone with 3.0 OS, but it wouldn't run on the 2.2.1 ipod touch2 because the GCC lib didn't have a symbol in it. I don't think it's possible to fix that, that's always been one of the major problems with GCC it's forward compatible but never backward compatible with the runtime libraries.But yea I did hack for about 30 minutes to get it to compile on GCC 4.2 a few months ago when 1.2 first came out.
#4
OS 2 only supports GCC 4.0 (similar to any *nix release actually that have such dependencies with their core).
GCC 4.2 requires a few additional thing that are part of the OS 3 core
09/06/2009 (10:14 pm)
There is nothing to fix.OS 2 only supports GCC 4.0 (similar to any *nix release actually that have such dependencies with their core).
GCC 4.2 requires a few additional thing that are part of the OS 3 core
#5
I got errors such as some "static" error that I needed to change the C++ Standard Library Type to Dynamic, which it already was, and changing to GCC 4.0 at the recommendation of this thread - I'll be honest, all this Xcode stuff is way above my head. I still think we need a walkthrough from the time right before we hit the Build button in iTGB all the way to the Build button in Xcode. That's where everything is all still shaky for me.
So, I gave up and wiped out my entire drive and did Snow Leopard from scratch, followed by Xcode 3.2 off the disc, then iPhone 3.0 SDK 4 SL, and finally iTGB 1.2.
I'm too exhausted right now to figure out if it works, everything's vanilla right now. What tweaks or changes should I worry about, specifically? Will all this be moot when 1.3 comes out?
09/09/2009 (12:46 am)
I was getting all weirdness trying to recompile the same code of Archangel and work on a new project with iTGB 1.2, after the reinstall of the Snow Leopard version of the iPhone SDK 3.0.I got errors such as some "static" error that I needed to change the C++ Standard Library Type to Dynamic, which it already was, and changing to GCC 4.0 at the recommendation of this thread - I'll be honest, all this Xcode stuff is way above my head. I still think we need a walkthrough from the time right before we hit the Build button in iTGB all the way to the Build button in Xcode. That's where everything is all still shaky for me.
So, I gave up and wiped out my entire drive and did Snow Leopard from scratch, followed by Xcode 3.2 off the disc, then iPhone 3.0 SDK 4 SL, and finally iTGB 1.2.
I'm too exhausted right now to figure out if it works, everything's vanilla right now. What tweaks or changes should I worry about, specifically? Will all this be moot when 1.3 comes out?
#6
Where'd I put my bottle of patience?
09/09/2009 (12:53 am)
3.0 compatibility (both running on OS 3.0 and building against SDK 3.0) was a mentioned priority. Take a break and hold on till 1.3 is out - that's what I'm doing right now :)Where'd I put my bottle of patience?
#7
09/09/2009 (5:03 pm)
Well, it looks like iPhone 3.1 SDK became official today when the OS 3.1 update came out. Are we still playing catch up, will this break the 1.3 roadmap?
#8
Downloading the SDK. Apple's servers are struggling :(
Upgrading the iPod was quick and painless.
09/09/2009 (5:13 pm)
The major changes were between 2.x and 3.0. 3.1.x only adds some new features to the OS, not to Xcode and the SDK (but there are likely to be bugfixes, so don't be afraid to upgrade).Downloading the SDK. Apple's servers are struggling :(
Upgrading the iPod was quick and painless.
Torque Owner Bret Patterson
After you install Snow Leopard you have to:
Install xcode 3.2
Download the new iPhone SDK 3.0 for snow leopard.
You won't see the SDK option in the drop down like your use to but you can still build for iPhone 2.2 or whatever.
To set your project to build for a specific version if iphone use:
Right click on target --> Get Info
Goto build options.
Set iPhone OS Deployment Target to the version of the OS you want to build for.
Make sure you build with GCC 4.0 or it will install but fail to run with missing symbol in GCC library on the phone.
Took me a while to figure it all out but I have it working fine now. I had to make a bug fix in the 3.0 SDK header file to get facebook to compile with GCC 4.0 but that's only if your using the facebook connect integration.