Re: Re[2]: PowerPC/Intel Weirdness
Re: Re[2]: PowerPC/Intel Weirdness
- Subject: Re: Re[2]: PowerPC/Intel Weirdness
- From: Dave <email@hidden>
- Date: Tue, 15 May 2007 15:55:41 +0100
Hi,
Thanks a lot, this fixed the problem. One thing though, I ran the
"install_name_tool" and changed it on a PowerPC, I verified it was ok
using "otool". I then copied the bundle onto an intel machine via the
LAN. When I looked at the file it on the Intel box it was still set
to a bad value. I changed it on the Intel Box and it works ok.
Is this correct? Should I need to set on on each platform?
Thanks a lot
All the Best
Dave
On 15 May 2007, at 14:51, Peter Mulholland wrote:
The first path you see from the output of otool -L is the path that
the linker will put in your executable when you link to your
dylib. If
you want to bundle it inside your app, you need to use
install_name_tool to change it. The recommended thing to change it to
is @executable_path/your.dylib
Further to that - once you've linked with them, you should put them in
the app bundle's Executables folder, using an Xcode "Copy Files" phase
Some people will tell you to use the app bundle's Frameworks folder.
In that case, change the paths to
@executable_path/../Frameworks/your.dylib and copy them into the app
bundle's Frameworks folder with a Copy Files phase.
--
Best regards,
Peter mailto:email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40looktowindward.com
This email sent to email@hidden
_______________________________________________
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