Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: static libraries

On Oct 21, 2005, at 10:42 PM, Steve Checkoway wrote:
On Oct 21, 2005, at 7:01 PM, Andreas Grosam wrote:
Guess, we need to *explicitly* specify
-L<lib-path> -l<name>
tupels in the "Other Linker Flags" build settings in order to ensure that a certain library will be selected.
(the -Wl, syntax is not necessary, though)

If you just pass -L/path/to -lfoo and expect it to give use /path/ to/libfoo.a and there is a dynamic library with the same name elsewhere, it'll get picked up unless you instruct ld otherwise by using -search_paths_first. Since gcc doesn't know about that, you have to use -Wl, to pass it along.

...just thought I'd mention a simple (non-xcode) way around this: just create a folder called "libs" or "staticlibs" and fill it with symbol links ("ln -s /path/to/staticlib.a staticlib.a") to your favorite/needed static libraries...then just include the path to this folder when linking...this makes all the dylib mix up go away :-)

james
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden

This email sent to email@hidden
References: 
 >static libraries (From: Steve Checkoway <email@hidden>)
 >Re: static libraries (From: Andreas Grosam <email@hidden>)
 >Re: static libraries (From: Steve Checkoway <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.