Write a custom catalog title here
CloudStack.Ninja is a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.com. To update CocoaPods you simply install the gem again. $ sudo gem install cocoapods. Or for a pre-release version. $ sudo gem install cocoapods -pre. If you originally installed the cocoapods gem using sudo, you should use that command again. Later on, when you're actively using CocoaPods by installing pods, you will be notified when new. Install cocoapods Mojave. Installing cocoapods on macOS Mojave, It looks like CocoaPods 1.9.0, the latest version as of this writing, depends on a newer version of Ruby than 2.3.7. But macOS Mojave only includes Ruby 2.3.7, It looks like CocoaPods 1.9.0, the latest version as of this writing, depends on a newer version of Ruby than 2.3.7. Brew based CocoaPods CLI fails in MacOS 10.15 Catalina due incorrect fallback to Ruby 2.3 #8955 Closed curiousapplications opened this issue Jul 1, 2019 56 comments.
Because the black apple system was reinstalled on the previous computer, CocoaPods was reconfiguredCocoaPods
What is CocoaPods?
ocoaPods is a tool responsible for managing third-party open source libraries in iOS projects. The source code of the CocoaPods project is managed on GitHub (https://github.com/CocoaPods).
The development of iOS projects inevitably requires the use of third-party open source libraries. When using third-party libraries, in addition to importing source code, integration of these dependent libraries also requires us to manually configure, and when these third-party libraries are updated, we also need It is very troublesome to update the project manually.
Macos Catalina Install Cocoa Pods Reviews
The emergence of CocoaPods allows us to save the time of setting up and updating third-party open source libraries. With CocoaPods, we can manage the third-party dependent libraries in a unified manner. Configuration and update only need to be completed with a few simple lines of commands.
Why use CocoaPods?
Before using CocoaPods, when a development project needs to use a third-party open source library, we need to:
Copy the source code of the open source library into the project
Add some dependent frameworks and dynamic libraries
Set -Objc, -fno-objc-arc and other parameters
Manage their updates
After using CocoaPods, we only need to put the used open source libraries in a file named Podfile, and then execute pod update. CocoaPods will automatically download the source code of these third-party open source libraries and provide it for us Set the corresponding system dependencies and compilation parameters for the project.
The principle of CocoaPods
The principle of CocoaPods is to put all dependent libraries in another project called Pods, and then let the main project depend on the Pods project, thus moving the source code management work from the main project to the Pods project.
Third-party libraries will be compiled into .a static libraries or .framwork dynamic link libraries for our real projects.
CocoaPods will combine all third-party libraries into a project named Pods in the form of targets, which will be placed in the newly generated Pods directory. The entire third-party library project will generate a static library named libPods.a for our project to use.
For resource files, CocoaPods provides a bash script named Pods-resources.sh, which will be executed every time the project is compiled, copying various resource files of third-party libraries to the target directory.
The original project settings have been changed. At this time, if we directly open the original project file to compile, an error will be reported. The Pods project where our project and third-party library are located will be organized and managed in the form of a newly generated workspace, which is convenient for us to intuitively manage the project and third-party library.
CocoaPods uses a file named Pods.xcconfig to set all dependencies and parameters at compile time
CocoaPods installation steps
Ruby environment
1. Set up ruby source
Macos Catalina Install Cocoa Pods Online
The ruby environment that comes with the Mac system will be installed
1.1, check the ruby source of your computer
ruby -v
Legend has it that the minimum version of ruby supported by CocoaPods is 2.2.2. If your computer version is lower than this version, you can upgrade ruby. The above shows that my computer version does not need to be upgraded. You can ignore the following upgrade operation
Macos Catalina Install Pod
Macos Catalina Install Cocoa Pods Free
sudo gem update --system
1.2 Replace ruby mirror
Ruby's default original address is a foreign network address. Use the following command to view the current mirrorgem sources -l
Remove current mirrorgem sources --remove https://rubygems.org/
Add domestic ruby mirrorgem sources -a https://gems.ruby-china.com/
Check the current mirror again and find that it has been replaced successfully
Macos Catalina Install Cocoa Pods For Sale
CocoaPods installation
Before Mac OS X 10.11sudo gem install cocoapods
After Mac OS X 10.11sudo gem install -n /usr/local/bin cocoapods
Since the system of this machine is 10.15, choose the latter command inputsudo gem install -n /usr/local/bin cocoapods
2.2, check whether the installation is successful
pod search AFNetworking
I actually looked at this blog configuration at the beginning, but at this step I found that there seems to be a problem
Opened the website https://git.coding.net/CocoaPods/Specs.git
found this look
But the principle is
The Podspec files of all projects are hosted at https://github.com/CocoaPods/Specs. When pod setup is executed for the first time, CocoaPods will update these podspec index files to the local ~/.cocoapods/ directory. This index file is relatively large, about 80M.
And I guess the reason for this is to clone the code of this repository
CocoaPods/Specs
https://github.com/CocoaPods/Specs.git
But the clone code from git is quite full, so it is put on coding, but this warehouse is out of date or private.
So I cloned a warehouse on Code Cloud
After changing the code link, it succeeded and the speed flew up