Home IOS Development BarCodeKit 1.4.0 | Cocoanetics

BarCodeKit 1.4.0 | Cocoanetics

BarCodeKit 1.4.0 | Cocoanetics


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 by way of Cocoapods and direct by way of GitHub, however these days 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 every thing to look Swift-native and so an implementer of such a package deal wouldn’t be the wiser.

To make it a Swift package deal I wanted to wash 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 package deal that will construct with out complains with a easy swift construct. However when you even have unit exams then you definitely need these to be conformant with the SPM ecosystem as nicely. This includes largely including the sources – if any – required by the check circumstances and including a check goal to the package deal.swift.

I used to be making some modifications after which working swift check, rinse and repeat. Each iteration you discover just a few extra minor issues you must tackle. Till ultimately each constructing and testing the package deal 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 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 Package deal 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 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 Package deal Index… it is because the license is a mix of my regular license and a full industrial license. Principally buying my ebook grants you a perpetual full industrial license. If you happen to don’t need to try this there’s my customary 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:

Classes: Administrative



Please enter your comment!
Please enter your name here