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 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 obtainable as Swift Package deal. 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 will construct with out complains with a easy swift construct. However in the event you even have unit exams you then need these to be conformant with the SPM ecosystem as nicely. This includes principally 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 adjustments after which operating swift take a look at, rinse and repeat. Each iteration you discover a number of extra minor issues you must 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 change into 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 eventually 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 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 surprise why it says “unknown license” on Swift Package deal Index… it is because the license is a mix of my regular license and a full industrial license. Mainly buying my e book grants you a perpetual full industrial license. If you happen to don’t wish to try this there’s my normal open supply license. Thereby you must attribute to me when utilizing BarCodeKit in your apps, or purchase a non-attribution license on my components retailer.

Tagged as: BarCodeKit

Classes: Administrative