Can't statically link library if a dylib exists?
Can't statically link library if a dylib exists?
- Subject: Can't statically link library if a dylib exists?
- From: Larry Campbell <email@hidden>
- Date: Thu, 30 Oct 2003 09:46:41 -0500
I've written a framework which is an Objective-C wrapper around
netsnmp. I've built netsnmp locally as a static library,
/usr/local/lib/libnetsnmp.a. I've added this static library to my
framework's target, but when I build the framework the static library
is not included, and the framework instead references
/usr/lib/libnetsnmp.dylib. The only way I've been able to get the
static version linked in to my framework is to delete or rename
/usr/lib/libnetsnmp*.
First, this seems like a bug. If I add /usr/local/lib/libnetsnmp.a to
my target, why is xcode even thinking about pulling in
/usr/lib/libnetsnmp.dylib?
And, more importantly, how do I get it to stop?
_______________________________________________
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.