Hi Lucas,
From everything you listed, only loading an abstraction from the same dir worked. I'll investigate in the addon's code itself and see if I can get it to work using `libpd_add_to_search_path()` somewhere.
Also, I might precise that usually I declare my externals using their folder name as a prefix, in this case [jl/gbend~ <name_of_table>] This frees me from having to use [declare] and avoids eventual name conflicts. Could this be an issue because of the library name not being the external's name when using [declare] ?
Thanks for your suggestions, Joseph
Le 13/02/19 à 11:58, Lucas Cordiviola a écrit :
Just a guess:
-- Can you load abstractions on those dirs?
if not:
-- Can you load an abstraction in the same dir as your "main-patch.pd"
If yes:
-- Can you load the [external] in the same dir as "main-patch.pd"
You can also test if [declare] is working. First with abstractions then with [external].
Mensaje telepatico asistido por maquinas.
On 2/13/2019 6:42 AM, Joseph Larralde wrote:
Hi,
A friend of mine wrote this libpd wrapper for nodejs (which is actually a work in progress) : https://github.com/ircam-jstools/node-libpd It's running fine on a pi3 I'm using ATM.
Now I need to use some externals I wrote, and I can't get them to load properly. But, they're loading when I start my test patch using pd itself.
Before diving into his wrapper code, I'd like to make sure I'm placing the externals in the right path. What makes me think it should be working is this page : https://github.com/libpd/libpd/wiki/misc And also the fact that in his code, he's calling the init() function from PdBase, which is itself calling the libpd_init() function.
I tried putting the externals into /usr/local/lib/pd-externals, /usr/local/lib/pd/extra, /usr/lib/pd/extra and ~/.local/lib/pd/extra. But still no luck ...
Can anyone confirm I'm not mistaken ?
Cheers, Joseph
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev