Dear pd community,

My pd "external" consists of a c library + pd abstractions.
I install them into the same directory:

$ ls -1 /usr/local/lib/pd-externals/structuredDataC/ 

I start pd with the -lib option (or add the library to the config):

$ pd -lib structuredDataC

Pd finds the objects exported from structuredDataC.pd_linux, such sdList. Right clicking even finds sdList-help.pd.
It doesn't find the normal abstractions, such as sdAnyBang.pd. Creating an [sdAnyBang] obj in a patch fails.

I know I could append the -path /usr/local/lib/pd-externals/structuredDataC/ option when running pd (or change the config accordingly) to make this work.

However I find this rather unelegant. The library is already in pds standard search path.

I would like the user to be able to import the library with one simple switch, relying on pds standard search directory.

Is there a way for me as a library author to make pd look for abstractions in the same directory as the imported library (similar like it does with -help.pd objects)?