diff --git a/Gemfile b/Gemfile index bc89fd6..53ac52a 100644 --- a/Gemfile +++ b/Gemfile @@ -3,7 +3,7 @@ source 'https://rubygems.org' gemspec gem 'xcodeproj', '~> 1.4' -gem 'cocoapods', '1.7.0' +gem 'cocoapods', '1.10.2' gem 'bacon' gem 'rake' diff --git a/README.md b/README.md index 39b328c..c53b76e 100644 --- a/README.md +++ b/README.md @@ -84,7 +84,7 @@ $ [bundle exec] rake pod:update ## Options If necessary, you can pass `vendor_project` options to the `pods` configuration -method. These options are described [here](http://www.rubymotion.com/developer-center/guides/project-management/#_vendoring_3rd_party_libraries). +method. These options are described [here](http://www.rubymotion.com/developers/guides/manuals/cocoa/project-management/#:~:text=bar.rb.-,2.6.%20Vendoring%203rd%2DParty%20Libraries). For instance, to only generate BridgeSupport metadata for a single pod, which might be needed if a dependency that you’re not using directly is causing issues (such as C++ headers), you can specify that like so: