I’m currently adapting a plug-in, that already functions in Linux and Windows, for MacOS and ran into a state where OpenMP traps the program complaining about a second OpenMP library being loaded. I’m wondering what the reasoning is for using @loader_path/…/Resources/lib/libiomp5.dylib rather than @rpath/libiomp5.dylib? Am I’m missing something on how to link with the libiomp5.dylib so that it doesn’t trap?
Based on what I’ve read it seems like @rpath is the correct way to address this problem. Wasn’t sure if this was a bug type of thing or not so I thought I’d inquire here first.