site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Jan 13, 2010, at 3:44 AM, Arnab Ganguly wrote: —Jens _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... What would be the best practises for the frameworks that are not available in iPhoneSDK but present in MacOSX SDK to be made available in iPhoneSDKs. Rewrite your code to stop using those frameworks, is probably the best advice. You can file a request with Apple, but who knows if/when they'll do anything about it? Porting over open-source framework sources is conceivable, but can easily turn into a huge amount of work if you can't get those sources to build or run on iPhone (which might be one reason they're not there to begin with...) Also, you mentioned you're building a dylib. Are you aware that iPhone apps can't contain embedded dylibs or frameworks? I'm not sure why, but this is an Apple requirement. You can build modules as static libraries and then link them into your app, though. This email sent to site_archiver@lists.apple.com