Interpreting -bind_at_load warning?
Interpreting -bind_at_load warning?
- Subject: Interpreting -bind_at_load warning?
- From: Jim Correia <email@hidden>
- Date: Fri, 11 Nov 2005 14:19:46 -0500
I have a project that builds a command line tool. The project has
been around since the Project Builder days, and upgraded with each
release.
When building with Xcode 2.2 it now generates the warning:
/usr/bin/ld: warning suggest use of -bind_at_load, as lazy binding
may result in errors or different symbols being used
The only reference I can find to this is at
http://developer1.apple.com/documentation/DeveloperTools/Conceptual/
DynamicLibraries/Articles/DynamicLibraryUsageGuidelines.html
The dynamic loader loads an image’s dependent libraries when the
image is opened; that is, when an application is loaded or when an
dynamic library is opened. The dynamic loader binds references to
symbols exported by dependent libraries lazily. Lazy binding means
the symbol references are bound only when the image actually uses
the symbols. As a debugging measure, you can specify that all
references to the exported symbols of a library be bound when the
dynamic loader opens the library. You use the gcc -bind_at_load
flag when generating the dynamic library.
Besides blindly taking the warnings advice and adding the flag to the
link flags, I'd like to understand the implications of doing so.
Is there something else I should read? Can anyone offer insight?
(Is this an uncommon flag? It doesn't appear, as far as I can tell,
in the target settings editor.)
Thanks,
Jim
_______________________________________________
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