Make Podspec working about carpaccio

[mz2]

Oh, thanks a lot! I actually tried making the Podspec at a stage where cocoapods was not working very well with Xcode 8 yet (the validation tool was not possible to run)… and I'm no expert in using it. However, Carpaccio should be a simple one as we don't do anything clever with build settings. I'll take a look at the iOS build I've recently added in the Xcode project and report back in a bit ->

[mz2]

Oh, that Xcode based build for iOS is actually happily building now (also tests, including on travis – that CI was failing for a while because of Xcode 8 issues as well).

This is the full set of source code files that should be compiled in:

Carpaccio/Carpaccio/ImageLoaderProtocol.swift
Carpaccio/Carpaccio/Collection.swift
Carpaccio/Carpaccio/CGSize+Extensions.swift
Carpaccio/Carpaccio/BitmapImage.swift
Carpaccio/Carpaccio/RAWImageLoader.swift
Carpaccio/Carpaccio/ImageMetadata.swift
Carpaccio/Carpaccio/Image.swift
Carpaccio/Carpaccio/BitmapImage+iOS.swift
Carpaccio/Carpaccio/Collection+Extensions.swift

[mz2]

Ah, that RAWConverter.mm was actually a remnant of our earlier RAW converter code which was based on libraw – we since moved over to CoreImage. I've dropped those source files now from the repo, altogether with libraw etc static libraries that were still in the repo and no longer necessary.

[MrZoidberg]

Just be sure to use the latest (currently pre-release) version of CocoaPods.

[mz2]

Thanks, that got me a bit further (progress pushed to master) – maybe you know how to finish this off?

• I've now got as far as having pod spec lint fail as it's evidently using the Swift 2.3 compiler to build.
• Based on what I've read (I'm a Carthage man myself, not used cocoapods really in production), fixing this doesn't appear to be a Podspec level issue but that there are presently some hacks on the level of a Podfile to make cocoapods behave.
• Not sure how I would incorporate any of that into actually checking this pod validates?

[mz2]

Looking at your fork btw, the Includes directory, the header search paths entries pointing at it, all the static libraries btw are all actually unnecessary and I've removed those today evening now from confusing people from the repo (they all predate the actual CoreImage based form of the code).

All in all this should really be as simple a pod as it gets – the Xcode configuration literally just compiles that handful of source files and links against AppKit / UIKit.

[MrZoidberg]

I'll investigate tomorrow. As far as I understood, you need CocoaPods 1.1.0.rc.2 for Swift 3.0

[mz2]

Yep, it seems to all work now – pod install / update works with the Swift compiler version set in the containing target. Tested with this tiny Podfile hooked to a made up Foobar Xcode macOS app target:

target 'Foobar'
platform :osx, '10.10'
use_frameworks!
pod 'Carpaccio', :git => '[email protected]:mz2/Carpaccio.git', :branch => 'master'

(iOS should be fine too)

What I wasn't able to work out yet successfully is how to get pod spec lint to behave with it. This may be why cocoapods 1.1.0.rc.2 still a prerelease :-)

[mz2]

Yep, a few more tweaks were still necessary, now up – the Swift compiler version can now be hinted for pod spec lint by creating a .swift-version file in the repo.

[mz2]

Please reopen if you hit any issues with building Carpaccio as a cocoapod.