Dynamic libraries, shared libraries, frameworks, and bundles are all loaded at runtime. The libraries and frameworks should go in <your plug-in bundle>/Contents/Frameworks/, and bundles usually go in <your plug-in bundle>/Contents/Plug-Ins/. Static libraries actually become part of your executable during compilation and linking, so you don’t have to copy them into your bundle.
Without more information, it’s difficult to say what the problem is. In general, if you are missing a dynamically loadable piece, you’ll see console output that says that dyld, the dynamic loader, could not find the particular library, so your plug-in could not be loaded. So I’d check the console and see what that says.
Darrin On Nov 11, 2013, at 2:44 PM, Ardo Avancena < email@hidden> wrote: What about dynamic libraries? Should it work the same way as the static libraries?
Then I tried copying the .fxplug product to a different computer and created a sym link in /Library/Plug-Ins/FxPlug/ folder but my plugin couldnt be found. Then I tried loading it in a different computer and installed the libraries since it had xcode, using the './configure' , 'make' and 'make install' on all libraries and copied the .fxplug product in the /Library/Plug-Ins/FxPlug folder and ran motion. My plugin showed up but whenever I try selecting it, nothing happens.
Any thoughts on this?
|