Subsequent month marks the 10 yr anniversary of BarCodeKit. It’s been like two years of slumber for the reason that final launch. It was obtainable through Cocoapods and direct through GitHub, however currently a number of builders voiced curiosity for it to be obtainable as Swift Bundle.
Like most of my open supply frameworks on GitHub, BarCodeKit is written in Goal-C, however that doesn’t imply it couldn’t be obtainable as Swift Bundle. Xcode automagically morphs all the things to look Swift-native and so an implementer of such a bundle wouldn’t be the wiser.
To make it a Swift bundle I wanted to scrub up some methods how system frameworks are imported, what headers are imported the place and most significantly I needed to ditch the precompiled headers (PCH) which aren’t supported by SPM.
As soon as that was carried out I had a bundle that will construct with out complains with a easy swift construct. However if you happen to even have unit exams then you definately need these to be conformant with the SPM ecosystem as effectively. This entails largely including the assets – if any – required by the take a look at instances and including a take a look at goal to the bundle.swift.
I used to be making some adjustments after which working swift take a look at, rinse and repeat. Each iteration you discover a number of extra minor issues you need to tackle. Till ultimately each constructing and testing the bundle go with out errors.
The end result of this train – I like to inform myself to justify all this time spent – is that your importing and setup has turn out to be extra sturdy.
So right here we go. I submitted the brand new 1.4.0 model to Cocoapods, tagged it on GitHub as a launch on the grasp department, and eventually submitted an addition requisition to the Swift Bundle Index. It’s been some time since I had carried out that final (couple of years truly) so I used to be confused initially by a GitHub bot stating that some extra evaluation was required.
However that was resolved ultimately by Mr. Dave Verwer himself approving the merge. Many thanks, I’m honored, Sir!
And in case you marvel why it says “unknown license” on Swift Bundle Index… it’s because the license is a mix of my regular license and a full business license. Principally buying my guide grants you a perpetual full business license. In the event you don’t wish to do this there’s my customary open supply license. Thereby you need to attribute to me when utilizing BarCodeKit in your apps, or purchase a non-attribution license on my components retailer.
Associated
Classes: Administrative