relocatable dylibs (e.g. embedded frameworks) are

问题:

I just upgraded from Xcode 6 Beta 2 to Xcode Beta 3 and am now getting the following warning when building my project:

ld: warning: relocatable dylibs (e.g. embedded frameworks) are only supported on iOS 8.0 and later (@rpath/libswift_stdlib_core.dylib)

It is a warning but seems to mean my current setup will not work on iOS 7.1, which is my deployment target. How can I track down which frameworks are embedded, and how can I fix this for iOS < 8.0?

回答1:

This appears to be a bug of Beta 3. As pointed out by Apple Engineer on this post.

I have also been living with this warning when running apps on iOS 7.1 device.

回答2:

You see and add them on the project page when you select the target: tab General->Embedded Binaries (and they then appear in Build Phases->Embed Frameworks).

Embedded frameworks for OSX were available in Xcode 5, but not for iOS.

WWDC session regarding new features in Xcode 6 specifically promised dynamic frameworks for iOS 8 (someone please add citation when developer center comes back online). So far, with all Xcode 6 betas, I have had no problems compiling and debugging an app with frameworks on iOS 7.

But since this wasn't promised, frameworks for iOS7 is something you cannot depend on (e.g. this may stop working in later betas; an app with embedded framework for iOS 7 may be rejected, etc.). That may explain why they added an explicit warning.

There's not much you can do if this feature turns out to be indeed unsupported, other than remove the frameworks from the target and use static libraries as we did with Xcode 5. Or go the iOS8-only route.

回答3:

After using XCode 6.1.1 I am able to put the code on iOS 8+ iOS7.1.2 and iOS 6.1.3 Although the warning is still there but the app works absolutely fine on all the 3 OSs

====================== Lucky guy... My project keeps failing to compile after I referenced the PushKit framework.

The project is a new project created by Xcode with only 3 new functions for testing Push Notification.

The workaround is to put the PushKit framework as "embedded", but this is not a good solution since my working Xcode project will be generated from Unity3d. Making the changes manually will break the auto build process.

回答4:

I had this error after adding a C++ framework (DeepBelief) to a project. Adding an empty .cpp file to the project fixed it.

I'm using Beta4, and found the answer on the DeepBelief github site:

XCode may be skipping the standard C++ library, and that's needed by the DeepBelief.framework code. One workaround I've found is to include an empty .mm or .cpp file in the project to trick XCode into treating it as a C++ project.

回答5:

Read this github post from ReactiveCocoa

The bug is still present in XCode6 GM and so XCode6 final release:

Well, I get the exact same issue in xcode6GM no matter whether I create framework for swift OR objc :-[[[[[[[[[[[[[[[

According to Apple Extension Programming Guide:

You can make a containing app available to users running iOS 7 or earlier, but then must take precautions to safely link embedded frameworks when running in iOS 8 or later.

talking about app extensions, but if you read it, you can understand that this applies to embedded frameworks in general.

回答6:

this is happening because one of your embedded binaries's deployment target is lower than your applications target. lower your embeded binaries's building target and be fine.

this was the error cause in xcode 6.1.1

i was using xcglogger with deployment target ios 8.0, and my application's deployment target 7.0. set the xcglogger's deployment target ios 7.0 and problem solved.

回答7:

After using XCode 6.1.1 I am able to put the code on iOS 8+ iOS7.1.2 and iOS 6.1.3 Although the warning is still there but the app works absolutely fine on all the 3 OSs

Yes not able to submit the app for review. Had to do by changing the modern frameworks to Static libs.