Best practices for cross-project development (and version control too?)
Best practices for cross-project development (and version control too?)
- Subject: Best practices for cross-project development (and version control too?)
- From: "Lukhnos D. Liu" <email@hidden>
- Date: Tue, 1 Jul 2008 17:34:56 +0800
Hi,
I've done some research for my needs, but I'd still like to know if
there are better ways to do this. Namely, what are the best practices
when you have multiple Xcode project files and need to put them
together?
Our situation is like this. We have accumulated a few framework
targets in a project, and we're looking for better ways to make them
reusable. Building the frameworks and then copy the built product to
other projects is one way, but it's far from ideal.
Another option would be to add the Framework project to a new project,
and have the framework targets built in the new project. This has the
drawback that the build/ folder must be set globally in Xcode. In
particular, is there any way to have Xcode build another project's
targets in the project's default build/ folder, and then fetch the
built product to the current project? If this is do-able, then the
drawback can be mitigated.
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!
d.
_______________________________________________
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