2 ms·
This kind of thing is pretty cool, but I’ve learned to avoid them, because they can result in A) BIG clumps of code, and B) testing issues. I used to have a sp
by ChrisMarshallNY 6y ago
This kind of thing is pretty cool, but I’ve learned to avoid them, because they can result in A) BIG clumps of code, and B) testing issues.
I used to have a special shell script that I wrote, that used lipo to combine multiple binaries into an aggregate library. I probably still have it around, somewhere. I was fairly proud of it.
Also, I had to use static libs, which wasn’t a problem, as long as I didn’t mind a big executable that couldn’t be trimmed.
Over the years, I’ve learned (the hard way, since I’m a stubborn knucklehead) not to “end run” around Apple’s prescribed methodology.
Now that Apple has wrapped Swift Package Manager into Xcode, it lessens the need for “clumped” binaries (for internal projects).