ALRIGHT, I used to be capable of get the mission to construct! I do not know if there’s or will probably be a greater answer sooner or later. I did not suppose my answer would work, so I wasn’t too assured, nevertheless it took me about 4 hours to determine this out although it ought to take so much lesser for you
How I made the iOS 16 library construct with iOS 15:
It was a extremely lengthy course of however I forked the WhisperKit repo and created my very own, and added iOS 15 checks and altered the model necessities to iOS 15, as you possibly can see in my commit historical past.
The issue was that it was depending on one other repo as effectively, fortunately that was open supply as effectively. So I forked it too and made related adjustments, however my adjustments to the fork was not getting mirrored and I learnt I wanted to create a brand new launch, which I learnt do by going to the repo in GitHub -> Go to the Code tab -> Faucet on Tags -> Releases -> Draft a brand new launch -> Select a tag -> give a quantity larger.
After which reference this model within the WhisperKit code Package deal resolved & swift recordsdata. And it labored, I’m able to construct efficiently! Inside my code, I added a examine to guarantee that the library code is utilized by iOS 16 units and up
Ideas
To be able to work out the adjustments wanted rapidly particularly for large libraries, I like to recommend first specializing in altering iOS variations of your dependent packages simply so you possibly can add them to your mission. After which it can present you which ones code traces have points. I used to be capable of “Present In Finder” for the issue recordsdata and open in a textual content editor, then Overwrite the Learn-Solely recordsdata to do away with the errors one after the other. After which as soon as all have been mounted, I copied these file adjustments to the truly open supply bundle repositories I had cloned.
