Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS Xcode and iPhone SDK question
- Thread starter ctyhntr
- Start date
- Sort by reaction score
You don't need to: use the later SDKs and set the deployment target to the lowest target iOS you want. The system will prevent you using any APIs that are not available in the lower SDK (assuming you've selected one)
As part of my learning process, I have some useful open sourced code that I collected for reference and compiled in the previous xcode and sdk (3.1). I know where to edit my base SDK settings (4.0) in Project Settings.
There is one project, where when I compile and launch in Simulator it comes up as a black screen. My first thought was delete the build folder, and then run and build. No dice, next was checking the View Controller and File Owner settings in Interface Builder. That appears correct, so I'm stumped.
I'm thinking if I go back to 3.2.2 and re-compile it in 3.1, then I can have something to compare. So, I'm trying to rule that out, actually avoid uninstalling Xcode 3.2.3 as a troubleshooting method.
There is one project, where when I compile and launch in Simulator it comes up as a black screen. My first thought was delete the build folder, and then run and build. No dice, next was checking the View Controller and File Owner settings in Interface Builder. That appears correct, so I'm stumped.
I'm thinking if I go back to 3.2.2 and re-compile it in 3.1, then I can have something to compare. So, I'm trying to rule that out, actually avoid uninstalling Xcode 3.2.3 as a troubleshooting method.
If you kept the previous SDK install .dmg file, you can (re)install the old one, then (re)install the new one in a separate directory. Then both SDK toolsets will be available for use.
I wasn't aware that Xcode could install in a different directory. I'll give it a try.
Thank you
Thank you
Yep, it says so in the Xcode Readme (see the Custom Install section). Probably one of the most important docs to read before installing new software.