Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Private frameworks vs. dylibs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Private frameworks vs. dylibs

Subject: Re: Private frameworks vs. dylibs
From: Jean-Daniel Dupas <email@hidden>
Date: Tue, 6 Jan 2009 19:41:19 +0100


Le 6 janv. 09 à 18:06, Michael Crawford a écrit :

I'm writing an application that presently includes some private frameworks.

Is there any particular reason they couldn't just by dylibs?  Is there
any advantage of private frameworks over naked dylibs?

They're built from some Open Source code.  When I compile, I don't use
any headers in the built frameworks, instead I un-tar the dependencies
in my project's folder and use the headers straight out of there.

Thanks!

Mike

The main advantage of a framework is that it is self contains. It contains Headers (useless for deployment) and resources (optional). The others advantage are versioning (useless for private framework). So if your library does not need any of these features, I don't see drawback to use dylib directly (as some projects do).


_______________________________________________
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



References:  
  >Private frameworks vs. dylibs (From: "Michael Crawford" <email@hidden>)




Prev by Date:
Re: Immediate Nib Loading Error

Next by Date:
Can't update Xcode 3.1.2 docs....

Previous by thread:
Private frameworks vs. dylibs

Next by thread:
Can't update Xcode 3.1.2 docs....

Index(es):

Date
Thread