static vs dylib lib linking
static vs dylib lib linking
- Subject: static vs dylib lib linking
- From: Kevin Packard <email@hidden>
- Date: Thu, 22 Feb 2007 13:59:39 -0500
What is the correct way to specify linking with "libfoo.a" instead of
"libfoo.dylib" if both libraries reside in the same directory?
I'm building a bundle that links to an external static library
libfoo.a. I added libfoo.a to my project by dragging it into the
xcode project. However, XCode tries to link with libfoo.dylib, which
resides in the same directory as libfoo.a.
When I look at the build transcript, I see the ln line contains "-
lfoo", so I've temporarily solved the problem by deleting
libfoo.dylib. However, I'd like to solve this correctly.
What's the right thing to do?
Thanks,
--
Kevin Packard
_______________________________________________
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