Re: Linking to third-party Frameworks and dylibs from a plug-in
Re: Linking to third-party Frameworks and dylibs from a plug-in
- Subject: Re: Linking to third-party Frameworks and dylibs from a plug-in
- From: Jean-Daniel Dupas <email@hidden>
- Date: Tue, 18 Mar 2008 21:02:30 +0100
Le 18 mars 08 à 20:06, Dan Korn a écrit :
A follow-up: It turns out that the framework I was linking to
didn't have a PowerPC executable binary. It seems that
install_name_tool will indeed modify both the PowerPC and Intel load
tables, but only as long as the framework or dylib to which you are
linking supports the same architecture on which you are building.
In other words, if the third-party framework or dylib is a Universal
Binary (ppc and i386), then install_name_tool will successfully
modify my plug-in's load tables for both architectures, regardless
of the architecture of the machine I'm using to build. However, if
the third-party framework or dylib only supports one architecture,
then install_name_tool will only work properly if you execute it on
a machine with that same architecture, regardless of which
architecture for which you're building your executable. In other
words, install_name_tool fails if the framework on dylib to which
you are trying to change the load path from your executable does not
support the current architecture. This seems to be a crack in the
armor of the Xcode postulate that you can build the same
executables, for any architecture, on any architecture.
Dan
And what it does if you run it as a PPC executabe ?
"arch -ppc install_name_tool -id .... " etc. _______________________________________________
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