Your last post is totally unhelpful.
I don't need to reduce the library file size. I just need to get this version of the framework to include properly in my application. Using 1.10.0 instead of A or B doesn't increase size appreciably. There has to be a way to pick B, unless Apple has just dropped all support for framework compatiblity. And if that is the case, how is it handled when an App uses frameworks F1(Ver B) and F2(Ver A), where framework F2 uses F1(Ver A)?
The current target is an OSX application, which is trying to embed the osx framework of the library.
The frameworks also have an iOS flavor, and I have an iOS version of the application in work too. I'm expecting to use this information for that as well.
I said that the library doesn't use A as the framework version identifier. And that the project option sign on copy does not work when trying to embed the library that is produced.
If the libraries were to update incompatibly, should it keep using a framework version A because it's going to be an embedded framework?
When the library generates it's output, it creates what looks to be a perfectly valid framework comprising of exactly one version of that framework.
XYZ.framework/Versions/1.10.0/....
XYZ.framework/Versions/Current -> 1.10.0
XYZ.framework/Headers -> Versions/1.10.0/Headers
XYZ.framework/Resources-> Versions/1.10.0/Resources
XYZ.framework/XYZ-> Versions/1.10.0/XYZ
There is more than just one framework
No other versions included in the framework folders besides the 1.10.0 for these. So, I am not trying to pick an old version of the framework while having later versions available. It's the only version.
For the area in the project, it is an embedded framework with a checkmark to sign on copy.
There is no place to add a bundle version. That's what I want to know how to do.
Including these frameworks in another project, the sign on copy fails with directory not found .../Versions/A.
Of course not, there isn't a Versions/A. Where does Versions/A come from? What do I fix in the library or the inclusion of the framework so xcode knows the version is 1.10.0?
If it has to always be A, how do you support breaking API changes in a framework that might get embedded?