But since the container will have to statically link in a copy of the framework's code, so it seems like there's no win until actually dropping 7.
Sent from my iPhone > On Apr 4, 2015, at 11:07, David Duncan <[email protected]> wrote: > > >> On Apr 3, 2015, at 11:39 PM, Rick Mann <[email protected]> wrote: >> >> So, I'm trying to add a Today Extension to my app that currently supports >> iOS back to 6.1. I'd like to continue to support 7, at the latest, and just >> not have a Today Widget prior to iOS 8. As a first pass, I created an >> embedded framework for all the common code. But then it wouldn't build with >> an iOS 7 deployment target, so I went searching, and found this: >> >> >> https://developer.apple.com/library/prerelease/ios/documentation/General/Conceptual/ExtensibilityPG/ExtensionScenarios.html#//apple_ref/doc/uid/TP40014214-CH21-SW3 >> >> Unfortunately, that just tells me I can't use the embedded framework prior >> to iOS 8, which means I need to link all the code into my container app and >> into my Extension redundantly, right? I can't think of a situation in which >> this conditional linking of code that can only be linked on iOS 8 is at all >> useful. > > Well, extensions don’t work prior to iOS 8 either, so you could leave the > framework in place for the future when you drop iOS 7 support. > >> >> Am I missing something? TIA, >> >> -- >> Rick Mann >> [email protected] >> >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Xcode-users mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/xcode-users/david.duncan%40apple.com >> >> This email sent to [email protected] > > -- > David Duncan > _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
