Subsequent month marks the 10 12 months anniversary of BarCodeKit. It’s been like two years of slumber for the reason that final launch. It was obtainable by way of Cocoapods and direct by way of GitHub, however these days 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 the whole lot 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 executed I had a bundle that may construct with out complains with a easy swift construct. However should you even have unit checks then you definately need these to be conformant with the SPM ecosystem as nicely. This entails largely including the assets – if any – required by the take a look at circumstances and including a take a look at goal to the bundle.swift.
I used to be making some modifications after which operating swift take a look at, rinse and repeat. Each iteration you discover a number of extra minor issues it’s important to deal with. Till in the long run each constructing and testing the bundle go with out errors.
The 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 strong.
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 at last submitted an addition requisition to the Swift Bundle Index. It’s been some time since I had executed that final (couple of years really) so I used to be confused initially by a GitHub bot stating that some further assessment was required.
However that was resolved in the long run by Mr. Dave Verwer himself approving the merge. Many thanks, I’m honored, Sir!
And in case you surprise why it says “unknown license” on Swift Bundle Index… it’s because the license is a mixture of my regular license and a full industrial license. Mainly buying my e-book grants you a perpetual full industrial license. When you don’t need to try this there’s my normal open supply license. Thereby it’s important to attribute to me when utilizing BarCodeKit in your apps, or purchase a non-attribution license on my components retailer.
Associated
Classes: Administrative
