Re: linking in private non-Framework libraries
Re: linking in private non-Framework libraries
- Subject: Re: linking in private non-Framework libraries
- From: Drew McCormack <email@hidden>
- Date: Mon, 30 Sep 2002 08:20:39 +0200
On Monday, September 30, 2002, at 07:59 AM, Glenn Howes wrote:
Unfortunately, it doesn't work. I thought it had, but that turned out
to be untrue.
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.
So I tried all sorts of things here, including the suggestion below,
and would like to get this working as I'm going to be driving home to
Minnesota (from CA) in the next few days so I want to fix this as soon
as possible. It doesn't seem practical to try to do anything with the
DB source, as the installation configuration and make file is
incredibly complicated.
Have you made sure the dynamic libraries are not in your project when
you build with the static library? And have you done a clean build to
make sure no object files exist that want to link to the dylib? That's
all I can think of: make sure there is no reference to the dylib
anywhere in the project, including the "Frameworks and Libraries" part
of the "Target" panel.
If that doesn't work, you could try moving the dylibs out of the
directory they are in, so they are not in the library path anymore, and
then doing a clean build.
Hope this helps,
Drew
... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...
... ... ... ... ... ... ... ...
Dr. Drew McCormack
Trade Strategist (www.trade-strategist.com)
Trading simulation software for Mac OS X
_______________________________________________
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.