Re: Dylib Dependencies (again)
Re: Dylib Dependencies (again)
- Subject: Re: Dylib Dependencies (again)
- From: Dave <email@hidden>
- Date: Wed, 6 Jun 2007 09:43:51 +0100
Hi All,
I tried that, and for PowerPC:
@loader_path/../../../../DynamicLibraries/
libfpacore2_uni.dylib (compatibility version 0.0.0, current version
0.0.0)
Which is correct, however for Intel:
/Users/admin/Documents/EngineAPI2/FPACore2/
libfpacore2_x86.dylib (compatibility version 0.0.0, current version
0.0.0)
Which is incorrect!
So, how do I set the dependency path for PowerPC *and* intel on the
build machine?
Thanks a lot for your help
All the Best
Dave
On 5 Jun 2007, at 23:39, Peter O'Gorman wrote:
On Tue, 2007-06-05 at 23:00 +0100, Dave wrote:
Hi All,
I finally figured out how to specify relative paths for libraries
that require a secondary library to be loaded. My build machine is a
PowerPC but I am trying to build something that works for PowerPC or
Intel based Mac's. I got this to work on the PowerPC and all was
well, I used "install_name_tool" (on the build machine - PowerPC) and
all worked wonderfully. But when I copy it to an Intel based machine,
the library path is not set correctly. Here is the path I am setting:
@loader_path/../../../../DynamicLibraries/libfpacore2_uni.dylib
The Library I am building is Universal and I build it from two files
(PowerPC and Intel) into one the dylib you see above.
I'm pretty sure that install_name_tool sets the install_name for every
architecture, but not at a mac to check.
You can do:
otool -arch ppc -L file.dylib
and:
otool -arch i386 -L file.dylib
To check the install names are the same (or not) for both
architectures.
Hope this helps,
Peter
_______________________________________________
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