Apple

I have never seen an Apple framework with more than a single version. Has anyone else ever seen that? In any event, if this is an embedded framework, then you don’t need all the old versions. Even if you did want to have all the old versions, I am pretty sure you would need to have all the versions in the framework. The only reason to have an “M” vs an “A” is so that an old version of your app can link to the “A”, “B”, etc. versions and new apps can link to the “Current” version. If you only have one version, I think it should probably be “A”, especially if it is embedded. I’ve always thought the versioning was a cool feature of frameworks, but I have never, ever seen it used in the wild.

John Daniel

email@hidden

On Oct 13, 2015, at 2:22 PM, email@hidden wrote:

I have written a framework that I want to embed in my application, but I can't overcome one issue. I'm using Xcode 7.0.1 on OS X v10.11 El Capitan. The framework project and the application project are in the same Xcode workspace, and the projects are correctly set up so that the framework will get linked by the application.

If I select the Codesign radio button in the target's General tab when I build the application, the build fails at the codesign stage with this basic error: "... Versions/A: No such file or directory". Well, of course it can't find a framework with version "A" -- my framework is now up to version "M" (I've been maintaining it for 13 years).

My question: I can't figure out how to tell Xcode to codesign framework version "M" instead of version "A". I have set every build setting I can find that takes a framework version to "M", but I'm guessing that I might have overlooked one. Can somebody please point me in the right direction? (Don't tell me to change the framework's version to "A"; that would be cheating.)