Re: Dylib Dependencies (again)
Re: Dylib Dependencies (again)
- Subject: Re: Dylib Dependencies (again)
- From: Greg Guerin <email@hidden>
- Date: Wed, 6 Jun 2007 16:10:35 -0700
Dave wrote:
>So, how do I set the dependency path for PowerPC *and* intel on the build
>machine?
This really ought to work, and the fact that it's not should raise
suspicions about something on your build machine being broken, damaged, or
seriously out of date.
What version of OS, Xcode, dev tools, etc. is on your build machine?
In particular, is your install_name_tool recent or old?
I just tried it here on 2 different Macs. This worked on OS 10.4.7 ppc,
and on 10.4.9 i386:
install_name_tool -id foo.dylib someFatThing.dylib
It changes the id on all the archs in the dylib, as confirmed by:
otool -L -arch all *.dylib
or:
otool -D -arch all *.dylib
And I even started with a someFatThing.dylib that happened to have
different id names for each arch, an artifact of an old build procedure I
no longer use.
Other than an old install_name_tool that isn't fat-macho aware, the only
reason I can think of that it wouldn't work for you is if the x86 dylib
doesn't have a long enough id-name area. That seems implausible, though,
because the new name is shorter than the old.
I recommend trying this with a much shorter name, e.g. "shortName.dylib",
just to see if install_name_tool does what it should. If it works, then
the problem is with the lib, although what it could be is still a mystery.
If the short name doesn't work, then the problem is with the tool or the OS
version, or something really strange.
If nothing else works, you can change the install-name on each
arch-specific dylib before you lipo them together, but you shouldn't have
to use that work-around. It ought to work.
-- GG
_______________________________________________
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