macOS dlopen() from a dylib linked to a command line app failing

[infinitebuzz]

Nevermind all this. Turns out it was a naming issue between linux and os-x. Thanks.


Hi

I am porting an application from windows to OS-X and Linux. In the app, each of the executables loads a couple of dylibs (direct link), which in turn dlopen() more dylibs as plugins. To keep everything similar on all platforms, the executable and all the dylibs are in the same directory. This works fine when running from a wxWindows/Cocoa application, but the dlopen loads fail when running from a command line application. I have done a lot of searching, and I know that app bundles are preferred on OS-X, but it is mostly working link this. I have:
- Checked my cwdir is correct
- Linked the dylibs as @executable_path\<name>
- Tried @load_path\<name> as well on a couple
- Double checked the wxWindows loads properly
- Double checked the command line does not
- Linked one of the problem dlopen modules to the command line directly, which worked
- I made symbolic links in /usr/lib/xxx to the dylibs in my user directory as well, when no change

Does anyone have any idea what I can try to get this resolved?

Thanks, Jmes