> On Nov 27, 2014, at 13:12, ico <[email protected]> wrote: > > I just create a demo project to experience building my own framework. So > far everything works fine. However, if I set my app deploy target to > iOS7.0, and do the same for the framework target, then I get a warning: > "ld: warning: embedded dylibs/frameworks only run on iOS 8 or later". > > It seems the framework mechanism only works on iOS8, but if I just ignore > this warning, and run the app on simulator, everything works, I can call > the API from my own framework. > I just don't understand, what all these about? I still can build my own > framework and run on iOS7 or not? > > It would be very appreciated if anyone can explain the whole story. > > -- > ========================== > Life isn't about finding yourself. > Life is about creating yourself. > _______________________________________________ > > Cocoa-dev mailing list ([email protected]) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/max%40maxchan.info > > This email sent to [email protected]
There are some fundamental differences between iOS 7, iOS 8 and OS X dynamic
linkers.
iOS dynamic linkers are very restricted, in the sense that it will not load
dynamic libraries from just any random location. In iOS versions 5-7 the
dynamic linker only load two files when loading an app: the app binary itself,
and a shared system framework cache. Your app with a dynamic framework, when
started in vanilla iOS 7, will not load the framework at all. This is the
reason why there is a jailbreakers’ framework called MobileSubstrate, that
handles injecting dynamic libraries into a process, just to bypass this
limitation.
The dynamic linker on iOS 8 also loads the embedded frameworks of an app when
starting it. This permitted the dynamic frameworks to work.
The dynamic linker of OS X, as well as iOS versions 1-4, loaded all dynamic
libraries from several predefined locations, including
{~,,/System}/Library/Frameworks and your app’s Frameworks folder. This is why
the simulator works - it is using the OS X dynamic loader instead of iOS one
that is more restricted.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
