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 out there through Cocoapods and direct through 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 little 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 carried out I had a package deal that might construct with out complains with a easy swift construct. However in the event you even have unit exams then you definitely need these to be conformant with the SPM ecosystem as effectively. This includes principally including the sources – if any – required by the check instances and including a check goal to the package deal.swift.
I used to be making some adjustments after which operating swift check, rinse and repeat. Each iteration you discover a couple of extra minor issues it’s a must to handle. Till in the long run 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 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 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 in the long run 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 mixture of my regular license and a full business license. Principally buying my e book grants you a perpetual full business license. When you don’t wish to do this there’s my customary 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
