Re: Question about embedding a framework
Re: Question about embedding a framework
- Subject: Re: Question about embedding a framework
- From: Bill Cheeseman <email@hidden>
- Date: Tue, 13 Oct 2015 15:09:19 -0400
On Oct 13, 2015, at 2:34 PM, John Daniel < email@hidden> wrote:
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.
I should have mentioned that I worked around the problem by turning off codesigning when building the application and framework, and instead codesigned both by choosing that option when I got to the Xcode Archive stage. It worked perfectly, producing an application and an embedded framework that both pass all the codesign validity tests in Terminal -- despite the fact that the embedded framework has a single version "M" in it. And the application executes correctly.
In fact, it makes more practical sense to code sign it when Archiving instead of every time I build, anyway. |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden