cocoapods-show-podpsecs-in-project 0.1.0 → 0.1.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/.gitignore +1 -0
- data/Gemfile.lock +1 -1
- data/README.md +13 -3
- data/lib/cocoapods-show-podpsecs-in-project/gem_version.rb +1 -1
- data/lib/cocoapods_plugin.rb +1 -0
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: ad10b7dcb0ef3b67ca9e6978faa4620884c12bea
|
|
4
|
+
data.tar.gz: fea9991e38dce82960ed474d2cbe827b59421bb0
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 6f283c2c4fc98d0ec65ed276164bfd4bb1f35090101f37e83b2bed92ad49910558033a478c980cfbcf28b59ec6a0e662a681ec0906e33cb6041975e970d513c1
|
|
7
|
+
data.tar.gz: 565611a4961ef1f68b2bd812cdb52a2cf9528ccf315399d0a4299b96952be840dacf570adafb62f041a18512f5c5324c056bd4556e4ba8eeb1867e3925afaf2a
|
data/.gitignore
CHANGED
data/Gemfile.lock
CHANGED
data/README.md
CHANGED
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
# cocoapods-show-podpsecs-in-project
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
[](https://badge.fury.io/rb/cocoapods-show-podpsecs-in-project)
|
|
4
|
+
|
|
5
|
+
A CocoaPods plugin which shows all project related podpsecs in pods project, including all dependencies.
|
|
4
6
|
|
|
5
7
|
No need to lookup podspecs any more.
|
|
6
8
|
|
|
@@ -12,12 +14,20 @@ No need to lookup podspecs any more.
|
|
|
12
14
|
|
|
13
15
|
## Usage
|
|
14
16
|
|
|
15
|
-
Add this line to `Podfile`, and you are all set 🥳
|
|
16
|
-
|
|
17
17
|
plugin 'cocoapods-show-podpsecs-in-project'
|
|
18
18
|
|
|
19
|
+
Add this line to `Podfile`, and you are all set 🥳
|
|
20
|
+
|
|
19
21
|
After a `pod install`, all podspecs should be shown in pods project.
|
|
20
22
|
|
|
23
|
+
## Why
|
|
24
|
+
|
|
25
|
+
Recently I met a problem.
|
|
26
|
+
|
|
27
|
+
Xcode 10 does not bundle with `libstdc++6.0.9`, but some pods we depended on write `s.libraries = 'stdc++.6'` in their podspec and cause our project failed to build. It's pretty frustrating to lookup their podspecs one by one and try to figure out which pod depend on this library. But with this plugin, it's easy to search and locate which extacly cause this problem.
|
|
28
|
+
|
|
29
|
+
I suppose, this plugin should only be useful at some rate situation.
|
|
30
|
+
|
|
21
31
|
## License
|
|
22
32
|
|
|
23
33
|
MIT
|
data/lib/cocoapods_plugin.rb
CHANGED
|
@@ -8,6 +8,7 @@ module CocoapodsGitHooks
|
|
|
8
8
|
FileUtils.mkdir specs_dir_path
|
|
9
9
|
|
|
10
10
|
context.umbrella_targets[0].specs.each do |spec|
|
|
11
|
+
spec = spec.parent if spec.subspec?
|
|
11
12
|
path = "#{specs_dir_path}/#{spec.name}.podpsec.json"
|
|
12
13
|
File.open(path, 'w') { |file| file.write(spec.to_pretty_json) }
|
|
13
14
|
end
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: cocoapods-show-podpsecs-in-project
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.1.
|
|
4
|
+
version: 0.1.1
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- X140Yu
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2018-11-
|
|
11
|
+
date: 2018-11-16 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: bundler
|