Re: Can't statically link library if a dylib exists?
Re: Can't statically link library if a dylib exists?
- Subject: Re: Can't statically link library if a dylib exists?
- From: Matt Majka <email@hidden>
- Date: Sat, 1 Nov 2003 10:16:40 -0700
Have you tried adding <path>/libfoo.a to the
"Other linker flags" setting under "Build" ->
"Standard Build Settings" in the Target info
pane?
On Oct 30, 2003, at 8:24 PM, Larry Campbell wrote:
So, a little more detail. It seems that when you add a static library
(libfoo.a) to a target, xcode adds
-lfoo
to the ld command line instead of what I want, which would be
<path>/libfoo.a
Is there any way to get xcode to use the filename I gave it, instead
of turning it into a -l option?
_______________________________________________
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.