Re: Framework Major versions
Re: Framework Major versions
- Subject: Re: Framework Major versions
- From: Nick Zitzmann <email@hidden>
- Date: Mon, 18 Oct 2010 18:12:52 -0600
On Oct 18, 2010, at 4:50 PM, Alexander Cohen wrote:
> I'm about to make a change in the Major version of a framework ( new version will be B ). I've read through the docs and all but i'm not sure i understand how to set it up so i keep version A in my build but also build the new version B.
>
> Has anyone done this
Yes.
> and what should i do?
You need to either move version A off to a separate project with the same target, or clone the target in the same project, with a new major version & its associated changes. Then you build both targets, and the framework versions will be merged with the same bundle. I think the "current" symlink is set to whatever version was built most recently.
Keep in mind that framework versioning is usually unnecessary, unless you have added variables to a fragile superclass, or if you've removed some obsolete stuff that might still be in use by old code, or if a bug fix in the framework is causing regressions in existing apps, or something similar. IOW, you probably don't need to do this if you added new content, or if the framework is private & you also own the dependencies. So it would help to know why you want to do this...
Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden