Re: linking in private non-Framework libraries
Re: linking in private non-Framework libraries
- Subject: Re: linking in private non-Framework libraries
- From: Finlay Dobbie <email@hidden>
- Date: Mon, 30 Sep 2002 16:49:26 +0100
On Monday, September 30, 2002, at 06:59 am, Glenn Howes wrote:
I'll restate my problem. I'm trying to use a generic library (the
Berkeley DB 4.0) which I've downloaded from sleepycat.com. I've run
the configure utility and done the make and the install, and this
results in a set of libraries: libdb-4.0.a, libdb-4.0.dylib and
libdb-4.0.la being placed in my /usr/local/BerkeleyDB.4.0/lib
directory. I'm showing my ignorance here, but I take it the .a file is
a static library, the .dylib is a shared library and I don't know what
the .la file is. I can drop either the .a file or the .dylib into my
project and access the routines encapsulated within and have been
doing so for months.
Now I'm trying to distribute my application and of course anybody
trying to use the beta can't because it isn't linked into the package.
So the app refuses to start up and the console shows an error about
not being able to find the DB library in wherever it was when it was
dropped in.
Well if you use the static library then the library functions will be
incorporated into your executable, or if you are using the dylib you'll
have to include it in your app's bundle (and possibly have to modify
the install path, not sure).
-- Finlay
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.