Re: Best practices for cross-project development (and version control too?)
Re: Best practices for cross-project development (and version control too?)
- Subject: Re: Best practices for cross-project development (and version control too?)
- From: Sebastian Nowicki <email@hidden>
- Date: Tue, 1 Jul 2008 18:35:34 +0800
On 01/07/2008, at 5:34 PM, Lukhnos D. Liu wrote:
Another issue that's not exactly related to Xcode per se but still
has to do with project management is how we should layout our
version control systems (we use svn but are migrating to git). The
ideal situation would be to have different framework projects like
A.framework, B.framework, C.framework, and when we develop a project
Foobar, we have an easy way to fetch and update the source code from
{A|B|C}.framework, build them with their own indepedent project file
(but from Foobar project), and link/copy the built frameworks for
linkage and packaging of Foobar.
I hope my description isn't too fuzzy, and I appreciate any insight
on this situation.
Thank you!
When using git I would suggest making a separate repository for each
framework. If you really want to keep them together, you can use git's
submodules[1], although in my opinion they aren't worth it. You could
just make one large repository, but git seems to discourage that, at
least that's the feeling I get.
[1] http://git.or.cz/gitwiki/GitSubmoduleTutorial
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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