Re: Bundles and dylib lookup
Re: Bundles and dylib lookup
- Subject: Re: Bundles and dylib lookup
- From: Xochitl Lunde <email@hidden>
- Date: Fri, 5 Mar 2010 14:21:41 -0600
<xcode-users-bounces+xochitl_lunde=email@hidden>
wrote on 03/05/2010 01:35:10 PM:
> My .app packages looks like this:
>
> MyApp.app/
> Contents/
> MacOS/
> MyApp
> libA.dylib
> libB.dylib
> libC.dylib
> PlugIns/
> PlugIn1.bundle/
> ...bundle contents
> PlugIn2.bundle/
> ...bundle contents
>
> Both PlugIn1.bundle and PlugIn2.bundle are linked against libA.
> dylib, libB.dylib, and libC.dylib. The three dylibs have install
> names of @loader_path/libName.dylib. The bundles, however, cannot
> find libA.dylib, libB.dylib, or libC.dylib. I've tried setting
the
> -bundle_loader flag to link against the main executable, but that
> didn't help. Is it possible for the bundles to look up the dylibs
> from the MacOS folder of the .app package and not have to copy them
> into the bundle as well?
>
>
> Grant Limberg
>
> [image removed]
Did you try setting LD_RUNPATH_SEARCH_PATHS in your
Release version of your software? Plain name is "Runpath Search
Paths". I have changed this in my program and I don't have a
problem. My release uses an absolute path, but I think my debug build
uses a relative path and both of them work fine when finding their libraries.
I've also seen programs where the libraries are in MyApp.app/Contents/MacOS/lib,
but probably they set the runpath too.
Xo _______________________________________________
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