Description

This PR adds a podfile configured for 1.0.0. This will allow CocoaPods users to add PSTModernizer to their Podfiles using the following syntax:

pod 'PSTModernizer'

CocoaPods likes to have a single example project so instead of clobbering the existing two I added a third in the "CocoaPods Example" folder. I don't think this will satisfy the needs of pod try PSTModernizer but it's enough to show someone how to use the library. This can be improved in a future PR, if needed.

I left out tests as I didn't want to dictate what kind of unit or UI tests to be run. The CocoaPods example would be a good place to gather those tests, though, when runners and specs are decided.

TODO

These issues seemed outside the scope of this PR so I leave them to a repo owner to execute before this PR is merged.

Tagging 1.0.0

Because this podspec is marked for 1.0.0 this repo will need a matching tag. This tag can be accomplishes with the following command:

git tag -a 1.0.0 -m "1.0.0 release" && git push origin 1.0.0

After the tag is pushed the podspec can be linted using

pod spec lint

Releasing the podspec

The podspec will need to be pushed into CocoaPods' trunk. If you're not already registered with the trunk that can be done thusly:

pod trunk register [email protected] 'Peter Steinberger' --description='Office rMBP'

After registering the podspec can be pushed using

pod repo push PSTModernizer PSTModernizer.podspec --verbose

Hi,

I think adding this to Cocoapods would be nice. Here is a podspec file you could user :

Pod::Spec.new do |s|
  s.name     = 'PSTModernizer'
  s.version  = '1.0'
  s.license  = 'MIT'
  s.summary  = 'Makes it easier to support older versions of iOS by fixing things and adding missing methods'
  s.homepage = 'https://github.com/PSPDFKit-labs/PSTModernizer'
  s.author   = { 'PSPDFKit Labs' => 'https://pspdfkit.com/' }
  s.source   = { :git => 'https://github.com/PSPDFKit-labs/PSTModernizer.git', :tag => s.version.to_s }
  s.source_files = 'PSTModernizer/*.{h,m,mm}'
  s.requires_arc = true

  s.xcconfig = { 'CLANG_MODULES_AUTOLINK' => 'YES' }
  s.ios.deployment_target = '6.0'
  s.tvos.deployment_target = '9.0'

end

The minimum iOS version could be adjusted, haven't been able to guess which one would be used. To support cocoapod versioning I usually tag each new version, and change the version number in the podspec.

To push to Cocoapods :

# checks if the podfile is correct and the code compiles 
pod lib lint
# push to the public cocoapods repo
pod trunk push PSTModernizer.podspec

I'm not exactly sure what PST_PARTIAL_AVAILABILITY_BEGIN/PST_PARTIAL_AVAILABILITY_END should mean, but it seems like they have been forgotten in file defines:

PSTModernizer/PSTModernizer/PSTModernizer.mm:96:5: Use of undeclared identifier 'PST_PARTIAL_AVAILABILITY_BEGIN'
PSTModernizer/PSTModernizer/PSTModernizer.mm:96:5: Use of undeclared identifier 'PST_PARTIAL_AVAILABILITY_END'
PSTModernizer/PSTModernizer/PSTModernizer.mm:141:5: Use of undeclared identifier 'PST_PARTIAL_AVAILABILITY_BEGIN'
PSTModernizer/PSTModernizer/PSTModernizer.mm:141:5: Use of undeclared identifier 'PST_PARTIAL_AVAILABILITY_END'

From this snippet:

#if defined(__IPHONE_OS_VERSION_MAX_ALLOWED) && __IPHONE_OS_VERSION_MAX_ALLOWED >= 100000
#define PST_IF_IOS10_0_OR_GREATER(...) \
if (PST_IS_IOS10_0_OR_GREATER) { \
PST_PARTIAL_AVAILABILITY_BEGIN \
__VA_ARGS__ \
PST_PARTIAL_AVAILABILITY_END }
#else
#define PST_IF_IOS10_0_OR_GREATER(...)
#endif