Re: Update individual source files - not everything
Re: Update individual source files - not everything
- Subject: Re: Update individual source files - not everything
- From: Fritz Anderson <email@hidden>
- Date: Fri, 15 Feb 2013 11:19:18 -0600
| Presumably if different developers have different sets of files, these are experiments that may eventually be merged back into the final product, or components of different products.
This is the reason version-control systems have branches. Creating them is a pain on command-line Subversion, and merging is so painful that people tend to avoid branches. But it's much easier in Xcode.
Also (and I don't know if this will help you), workspaces are intended to be a convenience to an individual developer. They aren't meant to be shared. The project is the actual unit of work for a set of targets; the only technical consequence of having a workspace is that for the purpose of working within it, the derived-files directory is shared and it's easier to cross-link between the products.
— F On 14 Feb 2013, at 2:59 PM, Graeme Costin < email@hidden> wrote: I am working in Xcode 4.5.2 on a workspace for our app and the library it links with, but other team members are continuing with other Xcode versions with our app as a separate Xcode project.
How can I svn update source files WITHOUT also updating the app's project file (and thus messing up my development of the workspace approach)?
Earlier Xcodes would allow you to update individual source files, but the only thing I can find in Xcode 4.5.2 is an update for everything!
-- Fritz Anderson Xcode 4 Unleashed: 4.5 supplement for free!
|
_______________________________________________
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