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: "Lukhnos D. Liu" <email@hidden>
- Date: Tue, 1 Jul 2008 20:55:27 +0800
On Jul 1, 2008, at 8:15 PM, Jerry Krinock wrote:
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.
Oh, it's problematic when the project files are to be shared outside
of the house, for example when we share one framework project and one
main app project with a client of ours, then it becomes an intrusive
thing to ask them to set their Xcode that way... all the more so when
the comparison with Visual Studio (where the solution-project
relationship, although having their own problems, is quite a good way
of offering what we have in mind).
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.
I have tried that. My problem is that script doesn't seem to scale
well (perhaps there are better ways to automate it I'm not aware of)
as project grows, there is always some extra check to do, some extra
work...
Also it seems that if Xcode's Copy File Phase does more than what it
does now (e.g. if it can copy from another project's build/
<current_config_as_set_in_main_proj> directory, there'd be no such
problem either.
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