Re: Location of dylib's
Re: Location of dylib's
- Subject: Re: Location of dylib's
- From: Bob Ippolito <email@hidden>
- Date: Mon, 6 Dec 2004 12:00:50 -0500
On Dec 6, 2004, at 11:42 AM, Karin Kosina wrote:
Well, neither do you *have* to allocate memory before writing to it...
;)
There's a big difference, in many cases it's not possible or practical
to relink the dylib such that the header is guaranteed to be
sufficiently padded.
IIRC, install_name_tool definitely lets you know when it's going to
fail. I haven't used it in a while, as I wrote my own tools that do
more advanced dependency analysis and relocation, and mine definitely
will report an error if it's not going to produce a valid Mach-O
header. As I said, I have never personally seen a Mach-O header that
wasn't already sufficiently padded to do
@executable_path/../Frameworks/ relocation, and I've put a LOT of
Mach-O files through these tools.
-bob
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden