Fixing “Base SDK Missing” error with Xcode 3.2.5 and iOS SDK 4.2
How to fix the Base SDK Missing error after upgrading to Xcode 3.2.5 and iOS SDK 4.2.
But first things, first, here's the error I received while trying to compile one of the early projects from my iOS SDK workshop: "error: there is no SDK with the name or path 'iphoneos4.1'"
How to fix the Base SDK Missing error after upgrading to Xcode 3.2.5 and iOS SDK 4.2.
I attended both days of the conference and loved the other sessions as well as the venue, and, of course, New York, where we got to see Driving Miss Daisy with James Earl Jones and Vanessa Redgrave, eat at Bubba Gump's overlooking Times Square (what an experience), and enjoy the culinary delights of the excellent The National restaurant (where we had the most amazing Branzino), and knock back a couple of espresso martini's at the W Hotel (they serve the best ones I've had anywhere).
This intensive course will give you a solid foundation in developing with the iOS SDK (for iPhone, iPad, and iPod Touch), Xcode (both 3 & and the upcoming 4), and Objective-C. To see a more detailed outline of the course and get all the juicy details, please see the course's web-site.
I am teaching my iOS (iPhone/iPad) development course again this month in Brighton. Sign up today to take advantage of some cool special offers.
Here are a few notes to help you for when you decide to the same:
Some notes to help you migrate from XAuthTwitterEngine to MGTwitterEngine.
In March of this year, I created a Twitter library called XAuthTwitterEngine based on Matt Gemmell's awesome MGTwitterEngine library and the excellent work (and with the assistance) of a number of great developers (including Ben Gottlieb, Jon Crosby, Chris Kimpton, and Isaiah Carew, Steve Reynolds, and Norio Nomura). Back then, MGTwitterEngine didn't have oAuth/xAuth support and I built XAuthTwitterEngine as a stop-gap, with the intension of back-porting to MGTwitterEngine at some point.
Well, MGTwitterEngine has had excellent oAuth/xAuth for some time now and I finally got round to checking it out today only to realize just how much progress they've made. It's definitely time to deprecate XAuthTwitterEngine and start using MGTwitterEngine again (so I am back-porting Feathers to MGTwitterEngine at the moment).
I just released a demo project showing you how to use MGTwitterEngine and I've also deprecated XAuthTwitterEngine as that stop-gap is no longer necessary.