re:
re:
- Subject: re:
- From: George Warner <email@hidden>
- Date: Mon, 17 Nov 2003 10:33:13 -0800
> 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?
Same way as dynamic; then just go into the project settings and change the
"library style" from dynamic to static. Done. ;-)
> 2) Why do you recommend against static frameworks in favor of a dynamic
> framework in the app's bundle?
The least advantageous is that keeping that part of your code separate from
the main application make it easier to update that just code without having
to download/install the entire executable.
A better advantage is if that framework can be shared between multiple
applications then it can be installed in a single location instead of inside
each of those apps and you save disk space.
> 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?
Actually linking statically would have a faster launch time since there no
delays for late binding. All the addressing was determined at link time for
static libraries.
> What are the pros and cons I should consider when contemplating this decision?
The #1 advantage is re-usability. #2 is update-ability.
Primary disadvantage would be that you have additional file(s) to install
(unless you package the dylib inside your app's bundle).
--
Enjoy,
George Warner,
Schizophrenic Optimization Scientists
Apple Developer Technical Support (DTS)
_______________________________________________
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.