Re: Framework versioning practices
Re: Framework versioning practices
- Subject: Re: Framework versioning practices
- From: Sak Wathanasin <email@hidden>
- Date: Fri, 16 Oct 2015 13:15:18 +0100
- Importance: Normal
On Thu, October 15, 2015 13:12, Bill Cheeseman wrote:
>> I am certainly not the only person using multiple versions or versions labeled other than "A" in
>> shared frameworks.
I'm not too clear on whether you have multiple versions inside your F/W or just 1, but not called
'A'. If the latter, the easiest thing is to let XCode do the signing. I modified the "framework
versions" of one of our F/Ws to be 'B', told Xcode to sign it (release builds only), which it did.
Then I built the appl, which, amomg other things, embeds all components including the signed F/Ws,
then signs the appl and it's happy.
From the CLI (we use a python script on our CI system), I can codesign either the top-level F/W
dir or xxxx.framework/Versions/Current and it's happy. This is with Xcode 6 (XC 4, 5 & 7 work fine
as far as I know). Our build script follows what XC does, which is to sign the appl "inside out".
If you have multiple versions, I don't know how you would sign versions other "Current" without
explicitly specifying them. Are the older versions not already signed from the previous builds? My
(not extensive) experiments suggests that's what happens, unless you "clean" first.
Regards
--
Sak Wathanasin
Network Analysis Limited http://www.network-analysis.ltd.uk
3 Edison Buildings, Electric Wharf, Coventry CV1 4JA, UK
Registered in England No: 2407211
Phone: (+44) 24 7655 12 20 Mobile: (+44) 79 70 75 19 12
_______________________________________________
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