Re: header edits in framework bundle confuse me
Re: header edits in framework bundle confuse me
- Subject: Re: header edits in framework bundle confuse me
- From: Philip Aker <email@hidden>
- Date: Fri, 13 Jun 2008 15:37:58 -0700
On 08-06-13, at 14:44, Thijs Koerselman wrote:
I'm working in parallel on a framework and an application using that
framework. I have both in a separate XCode project, because
eventually I want to continue to develop the app separately.
If I try to compile the application, and there is an error pointing
somewhere in the framework headers, it's very tempting to resolve
the error from where the compiler is pointing. The problem is, by
doing so, you edit the header from the linked framework bundle, and
not the real header which is used for compiling the framework
(residing in the other project). So the edits don't have any effect,
and you have to make the changes again on the original header once
you found that you have been editing the wrong header.
I find my current setup very confusing. Is there a better approach
to this in XCode? Is there a way for me to make XCode warn me if I'm
editing the bundle header, or make them read-only when the framework
bundle is compiled?
One option is to add a framework target to your application project.
It will essentially be the same as your current framework project.
When you have worked out the bugs in the framework, duplicate the
project, rename things as appropriate and you'll have two separate
projects again. I found this technique useful when I was trying to
separate framework material from UI code in an app where they were
previously intertwined.
Philip Aker
echo email@hidden@nl | tr a-z@. p-za-o.@
Democracy: Two wolves and a sheep voting on lunch.
_______________________________________________
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