Re: Conditional dependencies (and linked libraries) in a Xcode project?
Re: Conditional dependencies (and linked libraries) in a Xcode project?
- Subject: Re: Conditional dependencies (and linked libraries) in a Xcode project?
- From: Jack Repenning <email@hidden>
- Date: Mon, 19 May 2008 14:53:04 -0700
On May 18, 2008, at 8:41 AM, Mattias Arrelid wrote:
Maybe it is. If you'd like to test new features, you'd try to merge
each interesting branch back to the trunk - locally without checking
in any code. Is that what you were thinking of?
I'm not getting a very clear view of the lifecycle you expect for
these features ("conditions"), which will make the wording of my
answer kind of messy, but short form: maybe so.
I didn't think there'd be any need to merge to trunk (either locally,
or in the repository) until you've convinced yourself that this
feature really should become part of the main product. Until that
time, there would be a branch for each of these features, probably
based on trunk (containing all the trunk stuff, as modified to use a
given new feature). Such a branch would be complete: it could be
built in order to create an installable copy of your product including
the particular feature.
If your lifecycle ideas include such an idea as "deliver this feature
to some customers but not others," then those who get the feature
would get a product built from the branch, while those who don't get
that feature would get trunk builds (or maybe some other branch). If
these variant-version branches last for some time (as they would if
you delivered them to a customer!), then you'd periodically need to
merge from trunk out to the branch (so the branch continues to have
the latest trunk stuff, as well as its particular variant features).
Some day, when you decide that this feature should go to everyone, you
merge it back into trunk (and probably retire the branch).
My essential point is that a variation like this includes some code
changes, and some changes to the build process (to include or exclude
the external libraries, for example), and perhaps other changes (new
tests? additional config files? icons? all that). All of this would
be kept in version control, so that anyone can check out a particular
branch -- one checkout -- launch Xcode, click build, and get the
particular variant they wanted.
-==-
Jack Repenning
email@hidden
Project Owner
SCPlugin
http://scplugin.tigris.org
"Subversion for the rest of OS X"
_______________________________________________
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