Hi Riccardo

Thank you for this hint. The trouble is that it is a precompiled 3rdParty-Dylib which i can‘t compile by myself.

Greetings ascorbin

The issue is still not solved. I had success with R19 & R20 on Windows with the same lib as DLL. On Mac I suspect System Integrity Protection and DYLD_LIBRARY_PATH. Do I need code-signing ?

greetings ascorbin

Hi Andreas

Thanks a lot for your detailed answer.
Concerning this additional build/Release sub directory. After a complete fresh install (unzipping ski.zip, running kernel_app.app/Contents/MacOS/kernel_app g_updateproject=/Users/lenaamrhein/PROGRAMMING/C4D/sdk and compiling) my folder structure looks like this:

Build path settings in Xcode

So these build/Release-Folder aren't intended? Is it a feature of Xcode 10.1 ?

greetings ascorbin

Hm, still the same issue...

I hope this is a beginners problem. So my setup is this:

my project file ( designfabric.vcxproj ) lies here:

Cinema 4D R20/sdk/plugins/designfabric/project/designfabric.vcxproj

was created with Project Tool
sources are beneath:

Cinema 4D R20/sdk/plugins/designfabric/source

Is this the right location ? (should it developed inside /plugins ? - guess no)
there is also a res folder with the dylib, here:

Cinema 4D R20/sdk/plugins/designfabric/res/libs/osx/libxl.dylib

If I compile and start Cinema with Xcode the plugin only starts if there is libxl.dylib here:

Cinema 4D R20/sdk/build/Release/libxl.dylib

How to distribute Plugins?
Is it only copying the .xlib somewhere in plugins ? Must it have a res folder? other things?

Strange thing is if I compile another project with Xcode than my old designfabric.xlib inside plugins find the dylib inside sdk/build/Release and shows up. I really don't get it. Im totally messed with the paths.

Quite desperated I begun to port the whole project to Windows C4D R 19. Everything compiled nice, dlls loaded, but it wasn't possible to copy these plugins to another windows machine (the c4dsdkexample either)... em... so Im back on Mac R20 and trying to explain my boss: ok, you have to start Cinema 4D by Xcode and its only working on THIS computer.

Hope you have some clues for me, Greetings ascorbin

Hi!

I have a very hard time to figure out where to put my 3rd party dylib. I'm on macOs High Sierra 10.13.6 with Xcode 10.1 trying to code a C++ plugin with this library -> http://www.libxl.com. Strange thing is everything compiles fine and even works if (Xcode controls C4D (though I don't understand why the compiler creates an alias-file in sdk/build/Release, the place where the plugin-.xlib-module finds the dylib). If I place my compiled lib into the default plugin folder and start Cinema 4D app alone my dylib and so my xlib could not be loaded. Where to put my dylib? I tried several folder and subfolder but I can't find the correct location. Is Xcode setting some global path parameters? Do I have to define paths in projectdefinition.txt for Project Tool ? Thanks for a hint.

greetings ascorbin