18 Jan
2007
18 Jan
'07
3:27 p.m.
On 1/18/07 5:31 PM, "Don Agro" <dagro@dogparksoftware.com> 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