understanding the -bind_at_load warning
understanding the -bind_at_load warning
- Subject: understanding the -bind_at_load warning
- From: Chris Silverberg <email@hidden>
- Date: Sat, 2 Oct 2004 13:07:27 -0700
Hello everyone,
When I compile my application, the linker generates the following
warning:
warning: suggest use of -bind_at_load, as lazy binding may result in
errors or different symbols being used
I'm having trouble understanding just why the linker is complaining
about this, when I dont see the same warning for other applications.
When I initially got this error, I read about -bind_at_load, and it
seemed like the right thing to do, so I added it to my linker flags,
and the warning went away. Although this seemed to work fine for about
the last year, for one individual it did not. In his case when my
application asked QuickTime to open a sequence grabber for capturing
from his iSight, QuickTime was unable to access the camera. So after
trying many other things, i stumbled onto the fact that removing
-bind_at_load solved the problem for this user.
So it doesn't seem that using -bind_at_load is always safe to do. I
tried to find discussions about this warning and found very little.
One thing I noticed... this user is running Unsanity's APE and I assume
some related modules. Perhaps there is some kind of conflict with APE
and applications that use -bind_at_load. Any hints as to (a) why i'm
getting the warning in the first place and (b) what I should do about
the warning... should I just ignore it?
thanks,
Chris
_______________________________________________
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