Re: Linked Library inclusion into Framework Project
Re: Linked Library inclusion into Framework Project
- Subject: Re: Linked Library inclusion into Framework Project
- From: Jerry Krinock <email@hidden>
- Date: Mon, 31 Dec 2007 19:31:59 -0800
On 2007 Dec, 31, at 15:38, Chris Hanson wrote:
Your executable size should not have grown like that. SQLite is a
dynamic library, not a static one, so it should not be built into
your framework.
Yeah, I was worried about that "dynamic"-ness. So, after being
convinced that the one which I thought was built wrong is actually
built correct, I found another problem which was causing my sqlite
calls to return 0. My project works now.
As to why my old framework project packed sqlite into its own
executable, making it static instead of dynamic, I don't know how I
did that. Will study that further if need be. I suppose that, by not
packing it in, there are pros and cons...
(a) Nice, smaller binary
(b) App is not as robust, because it relies on /usr/lib/.
(c) I will get different versions of sqlite:
In Leopard, 3.4.0
In Tiger, 3.1.3
In Panther, none
But of course these same arguments (b) and (c) apply to other system
components such as the Cocoa frameworks.
Is libsqlite3.dylib listed under the Link Libraries & Frameworks
build phase for your target? If not, you just added a reference to
it to your project, you didn't make it a member of a target.
Yes, I know all about that little "Target Membership" checkbox, etc.
Also, it's more helpful to not just say that you've looked at the
otool output, but tell us how you invoked it and what it is. otool -
L should tell you that your framework pulls in /usr/lib/
libsqlite3.dylib.
Yes it does, but that's moot now.
Thanks again, Chris.
_______________________________________________
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