Re: Does Xcode support a "DLL" concept?
Re: Does Xcode support a "DLL" concept?
- Subject: Re: Does Xcode support a "DLL" concept?
- From: Mark Wagner <email@hidden>
- Date: Thu, 17 Sep 2009 13:36:00 -0700
On Thu, Sep 17, 2009 at 13:26, Wayne Bishop <email@hidden> wrote:
> Hi Group;
>
> Just getting my feet wet with xCode and Objective-C. As a former .NET
> developer I am wondering if xCode supports the concept of code reuse through
> compiled objects. For example, using Visual Studio I can add project
> "references" to DLL's that expose additional functionality. Is there an
> equivalent concept / process in Mac development?
Several of them:
1) Static libraries - A static library is a single file containing
compiled code. It's linked into the final program at compile time, so
you don't need to worry about distributing it with your product or
version mismatches, but the code isn't shared between programs: each
has its own copy.
2) Dynamic libraries - This is the one that's most similar to the
Windows DLL: a single file containing compiled code that is linked to
at runtime. You probably don't want to use it, though, because of
some design mistakes that make installing them a pain.
3) Frameworks - This is what you want to use instead of dynamic
libraries. A framework is a package containing compiled code, the
header files for programming with that code, and any resource files
that the code needs. It's linked at runtime the way that dynamic
libraries are, but doesn't suffer from the mistakes Apple made with
dynamic libraries.
Incidentally, it's "Xcode", not "xCode". Some people will bite your
head off if you make that mistake too often.
--
Mark Wagner
_______________________________________________
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