Turns out the way to handle this seems to be: 1. Use an Other Linker Flag: "-weak_framework Parse" in the private framework target
2. Don't link to Parse in the Linker Build phase in the private framework target 3. Link as normal to Parse in the main app target. Clean the build folders all around, do the builds and the warnings are all gone. At least on Xcode 6.4... On Tue, Aug 18, 2015 at 10:23 AM, Jens Alfke <[email protected]> wrote: > > On Aug 18, 2015, at 8:48 AM, Steve Mykytyn <[email protected]> wrote: > > I'm linking to the Parse.com <http://parse.com/> frameworks in both my > app and in a private > framework of my own included in the app. This generates the linker warning > below. > > > If Parse provides their library in the form of a true (dynamic) framework, > you should use that and have both your app and your private framework link > against it. > > If they only provide a static framework/library, you can create a target > that builds that into a dynamic framework and exports the necessary > symbols, then do the above. > > —Jens > _______________________________________________ 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]
