Re: Linked Library inclusion into Framework Project
Re: Linked Library inclusion into Framework Project
- Subject: Re: Linked Library inclusion into Framework Project
- From: Chris Hanson <email@hidden>
- Date: Mon, 31 Dec 2007 15:38:05 -0800
On Dec 31, 2007, at 12:21 PM, Jerry Krinock wrote:
I want to include the sqlite3 library in a new framework project. I
have successfully done this in an old framework project. It seems
that all I did was add /usr/lib/sqlite3.dylib symlink to the
"Linked, making sure it had target membership. Then when I
recompile the old framework, I see that the executable size
increases by about 700 KB and when I run otool on it I see that
sqlite3 symbols are available. Great.
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.
So I likewise add sqlite to a new framework project. It compiles,
links and runs. But, calls to sqlite3 functions return 0. And when
I look at the executable size and otool output, it is apparent that
sqlite didn't get included.
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.
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.
-- 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