iOS development-remove already configured class libraries and remove Cocoapods

Introduction

We use Cocoapods to import some third-party libraries into our projects very efficiently, but there is a question: if you find that a class library does not apply, or even the entire cocoapods we do not want to hold in the project, then how do we get these things out of the project? This article describes how to remove one or more Third-party class libraries that have been configured in your project, and how to remove the entire cocoapods from your project (not in a terminal). Delete a class library that has already been configured in the project

1. Open the Podfile file in the Cocoapods,

Delete the selected Fmdb

2. Open the terminal CD to the current project directory and re-execute the pod install command. The output information is as follows:

If Xcode already has the Cocoapods plug-in directly clicks the Install Pods to be possible (proposed first clicks "Update Pods", then "Install Pods")

3.FMDB has been removed
remove Cocoapods in Project

If you feel that Cocoapods is making your project a problem, bad or even disgusting, there are ways to remove it from the project:

1. Delete the Podfile, Podfile.lock, and Pods folders and Xcworkspace files selected under the Engineering folder.

2. Open the Xcodeproj file, delete the Pods folder and Pods.xcconfig references and LIBPODS.A in the project:

4. Open the Build phases option, delete check Pods manifest.lock and copy Pods resources, and embeded Pods:

5. Complete, compile run, pass without error.

Summarize

Removing a class library from the project directly modifies the "podfile" file, but removing the entire cocoapods is a bit of a hassle, perhaps with other methods.

Also, if you accidentally delete a file when editing a project, such as Podfile.lock, Podfile,

Then we'll use the above method to remove the entire cocoapods first, then re-establish the podfile and reload the cocoapods using the pod Install command.