Re: Organizing .h and .m files.
Re: Organizing .h and .m files.
- Subject: Re: Organizing .h and .m files.
- From: Nelson Santos <email@hidden>
- Date: Fri, 5 Oct 2007 12:22:41 -0400
Hi Kyle,
Thanks for your reply. That is what I suspected. I think I might
end up taking your suggestion, or just to manually "Add existing
files..." to my project as needed.
Nelson
On Oct 5, 2007, at 11:57 AM, Kyle Sluder wrote:
Unfortunately, the level of granularity you desire far exceeds the
cross-dependencies that could be present in your code, and is quite a
bitch to maintain, frankly. And it won't necessarily be more
efficient than having one large static library with all your modules.
So your best bet IMO (after having run into this design tradeoff
before in my C code) is to group related utility functions into larger
modules and statically link against those. Of course you'll still be
able to #import specific header files, but you will wind up linking
against the entire library. Which is not necessarily a bad thing, it
promotes code reuse after all.
--Kyle Sluder
On 10/5/07, Nelson Santos <email@hidden> wrote:
I should clarify this part a bit. Setting the search path works
fine in
telling the compiler where to file a .h file that I've imported,
but not the
.m files.
On Oct 5, 2007, at 10:06 AM, Nelson Santos wrote:
Is there a way to make the compiler locate the associated .m file
automatically? I tried setting the header and library search
paths to point
to the .h and .m folders. That didn't work (I knew it wouldn't.)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gmail.com
This email sent to email@hidden
_______________________________________________
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