Project compile link with using Cocoapods

1. In project that uses Cocoapods, the entire compilation link process is roughly: compile each third-party library chain to deliver the. a file, and then pods rely on each third-party library compilation link to generate the. A file compilation link to the LIBPODS.A Static library, Finally, project relies on the LIBPODS.A compilation chain to deliver the executable program.

2.pods generated. A static library will be added to the project's frameworks, there will be a project link problem: Project is compiled on the basis of the LIBPODS.A library linked but the error link can not find the third-party library in the. m file??

The reason is: the LIBPODS.A static library in the frameworks inside the 1.project may not be generated by compiling the link under the current device (real machine or simulator), but project does not make a judgment on the link libpods.a. Causes a class file in a third-party library to be found after a third-party library has been compiled to generate. A files (normally,. m files in a third-party library are compiled to generate. A files, and project is not required to compile the. m file).

Workaround: Build active architecture, build setting, targets, project and pods, Goto, will select NO. (Not only the compilation link is delivered to the current frame of the project)

Project compile link with using Cocoapods