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: Jerry Krinock <email@hidden>
- Date: Tue, 1 Jul 2008 05:15:40 -0700
On 2008 Jul, 01, at 2:34, Lukhnos D. Liu wrote:
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.
I don't see why this is a drawback. I find it convenient and logical
to have all my builds from all my projects in one folder.
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.
This is the same as your first solution "Building the frameworks and
then copy the built product to other projects", except that, I
believe, you want it done automatically. You can do that, or whatever
you want, with a Run Script Build Phase. For example, because I don't
like the way Xcode selects which Build Configuration to copy, I have
written a perl script which I invoke with one line to copy whatever
frameworks are needed. The summary/short answer to your question is:
Yes, Run Script Build Phase.
_______________________________________________
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