Re: Static Library Equivalent of a Framework?
Re: Static Library Equivalent of a Framework?
- Subject: Re: Static Library Equivalent of a Framework?
- From: Brent Marykuca <email@hidden>
- Date: Sun, 16 Nov 2003 10:33:46 -0800
On Nov 15, 2003, at 11:00 AM, George Warner wrote:
While you can have static frameworks I don't recommend them. If what
you
want is to ship a single application that includes the library code
but you
don't want to have to install a separate framework from your app then
you
can just include the framework inside the application bundle. To work
it
only requires that the library's install path be
"@executable_path/../Frameworks" so the system can find it at runtime.
You
can strip the framework down to just the dylibs (no headers, etc.).
Thanks for your answer, George. It prompts a couple of more questions:
1) You say that you can have static frameworks. How do you go about
creating them, and are they handled by Xcode the same way that dynamic
frameworks are?
2) Why do you recommend against static frameworks in favor of a dynamic
framework in the app's bundle? I can see how linking a framework
statically might make launch time longer, but are there other reasons
that one is better than the other? What are the pros and cons I should
consider when contemplating this decision?
Thanks,
Brent Marykuca
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.