linking to a static lib and *not* a dynamic lib when both are present
linking to a static lib and *not* a dynamic lib when both are present
- Subject: linking to a static lib and *not* a dynamic lib when both are present
- From: Tyler Daniel <email@hidden>
- Date: Wed, 19 Mar 2008 17:17:25 +0900
Hi all,
So I'm hoping someone can tell me that my problems linking to static
libs late last night really were, as I hope, only nightmares.
As silly as it sounds, I can't find any way to tell Xcode (2.5 or 3.0)
to link to the *static* version of a library. I even suspect that all
library references are passed to gcc indiscriminately with "-l" options.
This behavior surprised me after I very carefully dragged the .a
version of the library and *not* the .so into Xcode. The reference is
even named libsomething.a. Hmm.
Of course, Google offered this piece of advice:
http://developer.apple.com/qa/qa2006/qa1393.html
What's this? apple.com was hacked by a script kiddie with a *very*
subtle sense of humor? A forgotten April Fool's joke, perhaps?
In short, somebody say it ain't so!
Tyler
_______________________________________________
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