<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Mmmh you might have found the clue ...<br>
Actually I built the externals against pd version 0.49-0 and it
makes sense that they load properly with the same version.<br>
node-libpd comes with an arm libpd binary which seems to come from
an older version of pd (added 1 year ago).<br>
I can already tell that it's not an architecture issue because
everything is working on my pi : the addon is loading and running
abstractions when used in a node program, and pd is loading and
running my externals.<br>
Only loading my externals from node-libpd doesn't work.<br>
Still trying to get a local version of node-libpd to work ... then
I'll replace the libpd.so with one that I'll build from the latest
version.<br>
I can't see another explanation.<br>
Do you know something about incompatibilities between different
versions of pd ?<br>
The libpd.so used by the addon is probably not older than 0.47<br>
<br>
<div class="moz-cite-prefix">Le 13/02/19 à 13:58, Giulio Moro a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:610789595.4856084.1550062734612@mail.yahoo.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div class="yahoo-style-wrap" style="font-family:Helvetica Neue,
Helvetica, Arial, sans-serif;font-size:16px;">
<div>If loading abstractions works, then it is possible that the
external you are trying to load is somehow incompatible. Was
it built for this specific architecture, against the same
exact version of PureData? Are the externals relying on any
external library? Are those libraries - if any - available on
the computer you are running this on?</div>
<div>I'd recommend you run a bare-minimum raw libpd program to
make sure the externals are loaded properly. </div>
<div>For instance, you can build and run the program in
libpd/samples/c/pdtest/ and verify that it can load your
externals successfully, so at least you can temporarily rule
out the node.js wrapper as the cause of the issue.</div>
<div><br>
</div>
<div>Giulio</div>
<br>
On Wednesday, 13 February 2019, 12:32:55 GMT, Joseph Larralde
<a class="moz-txt-link-rfc2396E" href="mailto:joseph.larralde@gmail.com"><joseph.larralde@gmail.com></a> wrote: <br>
<br>
<div>Hi Lucas,<br>
</div>
<br>
From everything you listed, only loading an abstraction from the
same <br>
dir worked.<br>
I'll investigate in the addon's code itself and see if I can get
it to <br>
work using `libpd_add_to_search_path()` somewhere.<br>
<br>
Also, I might precise that usually I declare my externals using
their <br>
folder name as a prefix, in this case [jl/gbend~
<name_of_table>]<br>
This frees me from having to use [declare] and avoids eventual
name <br>
conflicts.<br>
Could this be an issue because of the library name not being the
<br>
external's name when using [declare] ?<br>
<br>
Thanks for your suggestions,<br>
Joseph<br>
<br>
Le 13/02/19 à 11:58, Lucas Cordiviola a écrit :<br>
> Just a guess:<br>
><br>
> -- Can you load abstractions on those dirs?<br>
><br>
> if not:<br>
><br>
> -- Can you load an abstraction in the same dir as your
"main-patch.pd"<br>
><br>
> If yes:<br>
><br>
> -- Can you load the [external] in the same dir as
"main-patch.pd"<br>
><br>
><br>
><br>
> You can also test if [declare] is working. First with
abstractions then<br>
> with [external].<br>
><br>
><br>
> Mensaje telepatico asistido por maquinas.<br>
><br>
> On 2/13/2019 6:42 AM, Joseph Larralde wrote:<br>
>> Hi,<br>
>><br>
>> A friend of mine wrote this libpd wrapper for nodejs
(which is<br>
>> actually a work in progress) :<br>
>> <a class="moz-txt-link-freetext" href="https://github.com/ircam-jstools/node-libpd">https://github.com/ircam-jstools/node-libpd</a><br>
>> It's running fine on a pi3 I'm using ATM.<br>
>><br>
>> Now I need to use some externals I wrote, and I can't
get them to load<br>
>> properly.<br>
>> But, they're loading when I start my test patch using
pd itself.<br>
>><br>
>> Before diving into his wrapper code, I'd like to make
sure I'm placing<br>
>> the externals in the right path.<br>
>> What makes me think it should be working is this page :<br>
>> <a class="moz-txt-link-freetext" href="https://github.com/libpd/libpd/wiki/misc">https://github.com/libpd/libpd/wiki/misc</a><br>
>> And also the fact that in his code, he's calling the
init() function<br>
>> from PdBase, which is itself calling the libpd_init()
function.<br>
>><br>
>> I tried putting the externals into
/usr/local/lib/pd-externals,<br>
>> /usr/local/lib/pd/extra, /usr/lib/pd/extra and
~/.local/lib/pd/extra.<br>
>> But still no luck ...<br>
>><br>
>> Can anyone confirm I'm not mistaken ?<br>
>><br>
>> Cheers,<br>
>> Joseph<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Pd-dev mailing list<br>
>> <a class="moz-txt-link-abbreviated" href="mailto:Pd-dev@lists.iem.at">Pd-dev@lists.iem.at</a><br>
>> <a class="moz-txt-link-freetext" href="https://lists.puredata.info/listinfo/pd-dev">https://lists.puredata.info/listinfo/pd-dev</a><br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Pd-dev mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Pd-dev@lists.iem.at">Pd-dev@lists.iem.at</a><br>
<a class="moz-txt-link-freetext" href="https://lists.puredata.info/listinfo/pd-dev">https://lists.puredata.info/listinfo/pd-dev</a><br>
<br>
</div>
</blockquote>
<br>
</body>
</html>