Re: Dylib Dependencies (again)
Re: Dylib Dependencies (again)
- Subject: Re: Dylib Dependencies (again)
- From: Dave <email@hidden>
- Date: Thu, 7 Jun 2007 11:33:59 +0100
On 7 Jun 2007, at 00:10, Greg Guerin wrote:
I recommend trying this with a much shorter name, e.g.
"shortName.dylib",
just to see if install_name_tool does what it should. If it works,
then
the problem is with the lib, although what it could be is still a
mystery.
If the short name doesn't work, then the problem is with the tool
or the OS
version, or something really strange.
I tried this, ran install_name_tool on PowerPC, checked it with otool
the path is set ok. Copied it to the Intel machine, used otool and
the path is *NOT* set.
If nothing else works, you can change the install-name on each
arch-specific dylib before you lipo them together, but you
shouldn't have
to use that work-around. It ought to work.
The thing is I have 2 files, a .bundle file that is build as a
universal binary in XCode, and a third party dynamic library that the
plug-in uses. When I get the 3rd party library it comes as two
separate files for PowerPC and Intel. I then use lipo to create one
universal file.
However, this is the file that is *used* by the universal bundle
created in XCode, I set the path of the bundle file to point to the
newly created 3rd party universal file created using lipo as above.
Not sure what to do now.
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