Re: Library Style -> STATIC, still linking dynamically
Re: Library Style -> STATIC, still linking dynamically
- Subject: Re: Library Style -> STATIC, still linking dynamically
- From: Brent Gulanowski <email@hidden>
- Date: Tue, 19 Oct 2004 13:49:52 -0400
On Sat, 16 Oct 2004 18:40:49 +0200, Drew McCormack
<email@hidden> wrote:
>
> On Oct 15, 2004, at 4:50 PM, Brent Gulanowski wrote:
>
> > This is weird. I'm building with some libs that have dynamic and
> > static. My build style specifies Static, the linking command lacks
> > "-dynamic", but the dynamic versions are being used anyway. What
> > gives?
> >
> > (If I remove one of the dynamic libs, the program won't run and get a
> > missing shared lib error; and i can see the Shlib in the libraries
> > window when I pause the debugger.)
> >
> > Workaround is to temporarily hide the dynamic libraries?
> This is what I have always done.
> Either rename or move the dylibs out of the search path. Another option
> is to add the full paths of the static library files to your compile
> line, rather than using -l options.
>
> I've always thought this was an ugly hack, but as far as I know, there
> is no other way.
Just for the record, I thought I better specify that I'm wasn't using
the "additional linker flags" option to include my static libs.
Although obviously I should as that will solve the problem. I had
simply added the libraries to the project -- Xcode is creating the
-l<lib> flags.
Thanks everyone for the bonks on the head ;-).
--
Brent Gulanowski
http://www.boredastronaut.com
_______________________________________________
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