ios - Static library with cocoapod dependency: define in Podspec s.dependency, in Podfile, or both? -


i converting static library use in-house cocoapod, our host applications can pull in referencing in podfiles. static library in turn depends upon third-party pod called hockeysdk.

in static library's podspec, indicate hockeysdk dependency follows:

 # mystaticlib requires latest hockeysdk framework:  s.dependency "hockeysdk", "3.6.4" 

i indicate dependency in podfile in root directory of static library:

target "mystaticlib"    pod "hockeysdk", "3.6.4" 

this seems work fine - if reference mystaticlib in podfile of myapp, pulls in mystaticlib , magically pulls in hockeysdk dependency, , in world.

what difference between these 2 seemingly redundant mechanisms indicating hockeysdk dependency? why use 1 or not other or both?


Comments

Popular posts from this blog

javascript - Bootstrap Popover: iOS Safari strange behaviour -

Website Login Issue developed in magento -

Can the constants be defined inside a model file of a framework in PHP? -