Yes, use @loader_path. That is relative to the folder holding the
executable loading the dylib (that is, "." refers to that folder).
Acrobat does this in its browser plug-in (AdobePDFViewer.plugin).
Use install_name_tool to change the path that your executable uses to
find those dylibs (install_name_tool has a man page).
On Jan 18, 2007, at 7:27 AM, Alexey Proskuryakov wrote:
On 1/18/07 5:31 PM, "Don Agro" <[EMAIL PROTECTED]> wrote:
The dylibs in question have the @executable_path install name set and
can be loaded from a standalone application package but if I am not
mistaken when the plugin is loaded by Safari this @executable_path
install name is interpreted as the Safari MacOS package contents
folder not the one in my plugin.
Is there any way to change this ?
I think an install name relative to @loader_path can be used to
specify
such a dependency (never used it myself, though).
- WBR, Alexey Proskuryakov
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo/webkit-dev
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo/webkit-dev
