operating system agnostic plugin names

asked 2017-02-24 14:12:44 -0500

GlenH gravatar image

updated 2017-02-24 14:14:23 -0500

Is there a canonical solution to the problem of dynamic libraries having different extensions on Linux/OSX/Windows? There was a thread a while back that discussed it, but I couldn't find a resolution.

The problem is that on OSX, dynamic libraries are by default named libXXX.dylib, whereas on Linux they're libXXX.so. On WIndows they're libXXX.dll.

When you specify libraries as plugins to a model, for instance, this makes the model architecture dependent. Not ideal.

Here's the original thread I found:


edit retag flag offensive close merge delete