I wasn’t talking about what might or might not be documented. In “Anatomy of Framework Bundles”, Apple documents how the bundle should look and how multiple versions should be used. I don’t know how your framework looks. Does it have a “Current” link and does it point to “M”? I can see how it might look for other versions and attempt to sign them. In general, my point is that it is usually a bad idea to be the only person exercising a particular feature. You ship against released operating systems, not documentation. Worry about what they do, not what they are, or were, supposed to do.
Also, it doesn’t sound like you have your workspace setup correctly. I strongly suggest that your workspace be completely self-contained. The workspace should be the one building your framework. The only exception might be external, multi-platform, multi-architecture static libraries. I’m not sure if even that approach will be viable for the future. Let Xcode build it all and sort it all out. John Daniel [email protected] > On Oct 13, 2015, at 3:00 PM, [email protected] wrote: > > You raise some interesting points that had not occurred to me. I'm surprised, > however, that I have never seen anything in Apple's documentation that > suggests you have to use version "A" for an embedded framework if you only > have one version in the framework bundle. > > The reason I'm up to "M" is that for several years I distributed my > application with an installer that installed the framework as a shared > framework in /Library/Frameworks/. I included the several most recent > versions (J, K, L) because several of my applications use the framework and > customers might have a newer version of one product that required version L > and an older version of another product that required version J or K. That's > what the letter versioning system is for, as I understand it, and the fact > that I eventually removed versions A - I never caused any difficulty. Now > that I'm switching to embedding the framework (as now recommended by Apple), > I only need the one framework version that works with this version of the > application. I assumed that I could just leave it labeled "M", which among > other things would avoid confusion going forward (although, of course, I can > tell the framework versions apart by build version and product version, too). > > If apple's rule is that a single embedded framework must always be versioned > as "A", that would explain why I can't find any way in Xcode to tell codesign > to sign version "M". But I would feel more comfortable if somebody could > point me to some official Apple document that says so. Any takers?
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
