thanks a lot! I guess I'm (partly) getting it. Not very much unlike the command line with all the libraries you had to write into the console about 30 years ago, now this activation has to happen from within the patch. Which now actually worked out in the case of "zexy" but not (I got courageous) in case of "Gem". Uploaded Gem and wrote a "declare -lib Gem" object into the patch - but its still not finding "Gemhead" (object) or the like. Tried "declare -lib Gem -path Gem" which caused some fuzz in the console (cannot open shared object file: no such file or directory), so it seems to be better without -path.

thing is -
I go into the zexy folder, click for example "mean-help", pd opens console, new window etc. and so does "mean". Fine.
I can open any other zexy object from within that new window.
I close everything, open pd, try to open for example "mean" and get: "couldn't create".
Tried: declare -lib zexy -path zexy.
I get:
bash: declare: -b: invalid option
hm.

not sure whether this is a technical issue. Anyway -
Downloaded pd 0.54
I run Ubuntu 18.04 LTS
also downloaded zexy
path
/home/Documents/Pd/externals
that's how it is listed under preferences.
Now my old patches have zexy objects (demux for example) - when I open them from within the pd console the zexy objects are not activated.
When I click directly on an obejct from within the zexy folder it opens.
I checked preferences and saved.
Any help?