Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Using .dylib with a CFM Application



On Thu, 19 Jan 2006 15:54:56 -0500, "Pierre Thibault" <email@hidden>
wrote:
> I have .dylib files not .so files. I don't know if it the same. I
> created a bundle in Xcode. Then, I added the .dylib, 5 of them, in the
> MacOS folder of my bundle. The problem that I have is with the
> references. I made a script that uses install_name_tool with the magic
> @executable_path word. But this is not working. I have to use absolute
> paths with my dylibs otherwise it does not work.

Note that install_name_tool can usually only change the install path if the
new path is not longer than the install path that the dylib was originally
built with. You should double check your dylib's path by using otool's "-L"
option. (I'd suggest building with the correct path in the first place and
not depending on the install_name_tool.)

> CFBundleGetFunctionPointerForName works properly. I have errors: "image
> not found". The same script that I use works fine when building an
> application with the dylibs instead of a bundle. If I look with otool
> -L, everything looks fine.

Can you post you "otool -L" output? Maybe it won't "look fine" to us. ;-)

> I really would like to use relative paths for my dylibs but it does not
> seem to work.

-- 
Enjoy,
George Warner,
Schizophrenic Optimization Scientist
Apple Developer Technical Support (DTS)


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden

This email sent to email@hidden



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.