Issues encountered with the introduction of third-party libraries by Swift and Objective-c mixed cocoapods (i)

The recent swift fire also wants to try to use it, considering that Swift comes out for a short time, and whether it is too mundane for Apple to update or not to develop existing projects with Swift.

Let's take a look at the problems I've encountered:

Question One,

The cause of the problem is that the build target file cannot generate more than one at compile time. It doesn't seem to understand what it means. Decisive Baidu!

The ultimate solution: http://stackoverflow.com/questions/24812983/ Xcode-archive-clang-error-cannot-specify-o-when-generating-multiple-output-fi

Seeing the answer, I saw hope. There are two places to change

1. Pod library file corresponding to target.

2. Target

See no: Empty the value of other C Flags. Compiled by.

problem two, and if the path of the pod library file is found to be inconsistent with the path of the current target, empty the directory:/users/user name/library/developer/xcode/deriveddata

Question three,

About Cocoapod use_framework! This east East don't know what is to do. I'm trying to understand, because I don't currently use the related class library of Swift, and do not find the benefits of using this!

Only know how to use use_framework! Third-party libraries are packaged directly into a static library!

Issues encountered with the introduction of third-party libraries by Swift and Objective-c mixed cocoapods (i)