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 22:35:26 +0100
Le 18 mars 08 à 22:14, Dan Korn a écrit :
On Mar 18, 2008, at 3:21 PM, Graham J Lee wrote:
On 18 Mar 2008, at 20:19, Dan Korn wrote:
On Mar 18, 2008, at 3:02 PM, Jean-Daniel Dupas wrote:
And what it does if you run it as a PPC executabe ?
"arch -ppc install_name_tool -id .... " etc.
I get this:
>arch -ppc install_name_tool
*error: arch takes no arguments
Can you really use arch that way? The man page doesn't mention
anything about passing it arguments or using it to modify other
commands. It just says, "The arch command displays the machine's
architecture type."
That arch behaviour seems to be 10.5+ only.
Okay, actually, when I try that on my 10.5 machine, arch does allow
me to specify the architecture under which to run another command.
Interesting. However, the man page on Leopard still doesn't mention
anything about this capability, although if you give it just the
"right" invalid syntax (or "arch -h"), the usage will give you
limited information on this feature. Is this documented anywhere?
I really am trying to be diligent about searching around and
figuring things out on my own before posting here, but this seems to
be another one of these hidden features which I would never have
been able to discover by following any of the standard "read the
documentation that came with the software" or "read the man page"
mantras, not unlike the @loader_path and @rpath options.
I suppose this "arch" trick might be useful if I were building a PPC-
only executable from an Intel machine running Leopard, but it
obviously doesn't help me at all when I'm building for Intel on a
PowerPC machine. There still seems to be a crack in Xcode's "build
on any architecture for any architecture" theory.
You could use lipo to extract the PPC portion of the binary which
then (of course) has to be run through Rosetta on Intel boxen.
Yeah, I suppose I could do something even more complicated,
depending on the architecture on which I'm building. But that's not
exactly what I was hoping for. I just want to be able to link and
load a third-party framework from my bundle without becoming an
expert on all these low-level tools and the inner workings of the
dynamic linker. That's why I'm using an IDE in the first place.
Thanks,
Building Intel only on PPC machine works well on Leopard but not on
Tiger, as Leopard is the first true Universal Binary Release of Mac OS
X.
Actually, doing "man arch" on Leopard give me this. Are you sure you
man path does not contains some old man page.
In fact, I'm not sure that man search in the Developer directory by
default. I think I have changed it the first time it returns me "no
man" (by adding an xcode entry /etc/manpaths.d/).
NAME
arch -- print architecture type or run selected architecture of
a universal binary
SYNOPSIS
arch
arch [-h] [[-arch_name | -arch arch_name]...] prog [args ...]
_______________________________________________
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