Subsequent month marks the 10 yr anniversary of BarCodeKit. It’s been like two years of slumber because the final launch. It was out there through Cocoapods and direct through GitHub, however recently a number of builders voiced curiosity for it to be out there as Swift Package deal.
Like most of my open supply frameworks on GitHub, BarCodeKit is written in Goal-C, however that doesn’t imply it couldn’t be out there as Swift Package deal. 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 executed I had a bundle that will construct with out complains with a easy swift construct. However for those who even have unit assessments then you definitely need these to be conformant with the SPM ecosystem as properly. This entails principally including the sources – 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 modifications after which operating swift take a look at, rinse and repeat. Each iteration you discover a couple of extra minor issues it’s a must 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 at last submitted an addition requisition to the Swift Package deal Index. It’s been some time since I had executed that final (couple of years truly) so I used to be confused initially by a GitHub bot stating that some extra overview 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 surprise why it says “unknown license” on Swift Package deal Index… it is because the license is a mixture of my regular license and a full business license. Mainly buying my ebook grants you a perpetual full business license. When you don’t need to try this there’s my normal open supply license. Thereby it’s a must to attribute to me when utilizing BarCodeKit in your apps, or purchase a non-attribution license on my components retailer.
Associated
Classes: Administrative
