Re: Dylib Dependencies (again)
Re: Dylib Dependencies (again)
- Subject: Re: Dylib Dependencies (again)
- From: Dave <email@hidden>
- Date: Thu, 7 Jun 2007 11:04:05 +0100
On 7 Jun 2007, at 03:44, Peter O'Gorman wrote:
On Wed, 2007-06-06 at 16:10 -0700, Greg Guerin wrote:
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
Yes, I just tried it too, it changed the install_name for every
architecture. The only thing that I can think of is that two libraries
are being created, one for each arch, install_name_tool is being
used on
one of them, then, after that they are made into a fat lib using
lipo(1).
I'm running MacOS 10.4.9 on a PowerPC G5 on the build machine, the
test machine is a Mac Pro again running MacOS 10.4.9.
The plugin itself is created using XCode set for universal build, I
set the path inside the Plug-In bundle, not the libfpacore2_uni fle.
The 3rd party dynamic library (the library I am trying to use from my
PlugIn) is given to me as two libraries:
libfpacore2_ppc.dylib
libfpacore2_x86.dylib
I then use lipo to create:
libfpacore2_uni.dylib
To do this I use the following command:
lipo -create libfpacore2_ppc.dylib libfpacore2_x86.dylib -output
libpfacore_uni.dylib
I then run install_name_tool on libfpacore2_uni.dylib which only
seems to set the
This is the dynamic library I am trying to use from my .bundle plugin.
Given this scenario, how do you recommend I proceed? If I could set
this path in XCode it would solve all my problems!
Thanks a lot
All the Best
Dave
_______________________________________________
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