Pre-compiled Libraries for iPhone OS

Digging into the RedLaser SDK. Their sample includes several ".a" files that seem to contain all the real magical guts of the their product. Intrigued. This link describes how to create such a thing for myself.

UPDATE: Here are a few other similar links:

• StackOverflow: A Guide for Creating your own Library for Cocoa(touch) development
• StackOverflow: Can I develop my own objective-C Framework for Cocoa Touch Applications?
• Building static libraries with the iPhone SDK
• StackOverflow: How do I add a third party Framework to iPhone project?

iPhone / iPad Universal Binary notes

Building a universal binary for iPhone / iPad seems a bit unintuitive. Started in XCode by selecting my target, then, in the menu, choose Project -> Upgrade Current Target for iPad…

After that, a build yielded the following warning:

"warning: building for deployment target '3.2' should omit the armv6 architecture."

Select the project, click Info, change the following values:

Base SDK: Optimized (armv6 armv7)

Build Active Architecture Only: NO

Targeted Device Family: iPhone/iPad

iPhone OS Deployment Target: iPhone OS 3.1.3

Should get rid of warning and build and debug on iPad.

When building for the iPhone, don't switch the build target back to 3.1.3. Keep using 3.2.

Free Version and in-app purchases

Researching building a free version of an iPhone app and a paid version of the same app that includes in-app purchases.

I got started by copying the target bundle in XCode to create MyApp and MyAppFree. One of my first questions is, how do I handle the bundle id and app id? Found this at StackOverflow that sent me in a slightly different direction:

http://stackoverflow.com/questions/2146097/app-id-and-bundle-seed-id-in-multiple-applications-with-aspn-inapp-purchase-and

particularly:

"…Apple has frowned on having both a "Lite" version as well as an "in-app" updatable version. One or the other. Recently they have been pushing the "in-app" updatable…"

uh oh ... led to this:

http://www.tuaw.com/2009/10/15/apple-relents-in-app-purchase-for-free-apps-allows-demo-to-paid/

So, can have one version of the app instead of free version and full version.

Next read was "App Store Quick Reference: Getting Started with In App Purchase on iPhone OS".

https://developer.apple.com/iphone/news/pdf/in_app_purchase.pdf

http://developer.apple.com/iphone/news/appstoretips/

I read no definitive prohibition against building both a free and an in-app purchase version, but feel that I should be better safe than sorry.