Xc frame making

How to tell? Is the framework a dynamic library or a static library?

Basic usage of lipo command

Introduction of the concept of multi-objective collaboration in projects

Those things behind the zsource command of Meituan iOS project

Implementation of the same "ZSource" binary debugging in iOS Meituan

/MeetYouDevs/cocoapods-imy-bin

Working principle and improvement of cocoapods-binary

Ruby and Cocoapods articles

Iospad "xxx.h" file was not found, and & ltangled & gt includes; Please use quotation marks instead.

The file caused by Pod was not found.

Cocoapods Finishing (3)-Compiling podspec files

View the application's signature:

codesign -vv -d xxx.app

View the signature of the library (also view the modes supported by the library):

codesign -vv -d xxx.framework

View all certificates installed on the computer:

Security Lookup-Identity-Vice President code signing

To re-sign the library:

Codesign -fs "Apple Development: XXX (XXX)" xxx.framework.

Xxx.framework/xxx archives

View supported architectures:

Xxx.framework/xxx Fat Information Company

Delete the specified mode (such as x86_64, the exported library will automatically delete the signature information):

Merge several architectures (for example, merge x86_64 of emulator and arm64 of real machine into one, one framework can support both real machine and emulator, and the exported library will automatically delete the signature information, but it will increase the package size).

Xcode can choose the architecture actually needed in xcframework to compile into the package at compile time, which can reduce the size of the package. An xcframework can support both real machines and simulators.

1. A project to create a frame in xcode.

2. Then create a Podfile. The source code of the framework depends on the third-party library using pod.

2. 1 If use _ frameworks in pod file！ It's open,

2.2 If you use _frameworks in podfile! Annotated or without such a sentence,

3. Matters needing attention in creating xxx.podspec

1. This file must be in the first-level directory under the git warehouse.

2. The name of 2.xxx.podspec needs to be the same as s.name = 'xxx' in the file, and this name is also the name of pod 'xxx'' in the main app.

3, the specified framework

4. Specify relevant third-party libraries:

Mode 1: Introduction through abstract mode.

Method 2: add pod to the cycle target.

Method 3: Extract and introduce the targets of the public pod.

The included iospod "xxx.h" file was not found; Please use quotation marks instead.

Good < >; You have to change it to "",or I will give you an error t t.

Analysis:

The corresponding path is not configured in the title search path. Probably because. Podspec file is not configured with corresponding dependencies, resulting in the path of the corresponding dependency library not being written into the "header search path" of the compiled project.

Solution:

Method 1:

Project-> Project-> Project XXX-& gt；; Information-> Configuration->; Debugging-> Project XXX-& gt；; target XXX-& gt； Pods-xxx.debug

Better change it to this. If there is a custom configuration, introduce Pods-xxx.debug into the defined configuration.

Method 2:

Modify the title search path

Add $(PODS_ROOT) to select recursion.

Add $ (srcrroot) to select recursion.

build