Hi all!
I am developing a plug-in. Now I need to recompile it with Mach-O
(create a Mach-O bundle package). The plugin itself uses numerous
dylibs which come from other developers and they couldn't be changed to
frameworks and etc. The dylibs were compiled with install path
"@executable_path".
The plug-in is located in application plug-ins folder. Now the plug-in
couldn't be loaded because it searches for linked dylibs in the
"@executable_path" (the path of the executable of the host application)
and couldn't find them there.
Actually I don't want to put dylibs in the folder of the executable of
the host application.
My idea was to develop another plug-in which is loaded before my
plug-in and loads all required dylibs with NSAddImage method. But it
seems that this approach doesn't work - application still tries to
search "@executable_path"
Does anyone know what can be done in such situation?
Any suggestion or idea will be deeply appreciated.
Many thanks in advance,
Konstantin
boga@mac.com - 26 Apr 2005 23:30 GMT
> Hi all!
>
[quoted text clipped - 18 lines]
> Does anyone know what can be done in such situation?
> Any suggestion or idea will be deeply appreciated.
We're using the NSAddImage for solving the same issue. We're using the
following options to NSAddImage:
NSADDIMAGE_OPTION_RETURN_ON_ERROR | NSADDIMAGE_OPTION_WITH_SEARCHING |
NSADDIMAGE_OPTION_MATCH_FILENAME_BY_INSTALLNAME
Did you provided NSADDIMAGE_OPTION_MATCH_FILENAME_BY_INSTALLNAME?!
Regards,
Miklós
Konstantin - 27 Apr 2005 15:53 GMT
Thanks a lot . It really works.
I haven't specified NSADDIMAGE_OPTION_MATCH_FILENAME_BY_INSTALLNAME
Regards,
Konstantin