i just made my first proper external, and was so super chuffed that i got it working.
i'm on osx, so using .pd_darwin extension.
i put it in my extra folder, made a demo patch in pd, and it works fine.
only problem is, when i shared the .pd_darwin with 2 friends, it didn't work for either of them. (i checked they had put it in the extra folder)
does anyone have an idea what might be wrong?
what sort of info can i provide to track down the issue?
i built for universal architecture.
friends are both on osx 10.10 same as me.
what could be the issue here?
Matt
On 2016-02-10 10:24, i go bananas wrote:
i just made my first proper external, and was so super chuffed that i got it working.
i'm on osx, so using .pd_darwin extension.
i put it in my extra folder, made a demo patch in pd, and it works fine.
only problem is, when i shared the .pd_darwin with 2 friends, it didn't work for either of them. (i checked they had put it in the extra folder)
does anyone have an idea what might be wrong?
how about:
tell them to Pd in verbose-mode ("-verbose"), and see whether the external can be found (and if it can't be found, this will give you a clue where Pd searches for the libraries).
if it can be found, try to find out whether the dylib loader throws an error (e.g. on the stderr/stdout; so you might need to start Pd from the cmdline).
do you use the same Pd version? Pd's API is very stable, but every now and then a new function is added. if you use such a new function in your code, then you cannot use the external with a version of Pd that predates the introduction of said function).
do you (dynamically) link against non-standard libraries? are they present (and in a searched-for location) on your friends machine?
fgmasdr IOhannes
thanks IOhannes,
verbose mode helped us realise that the file wasn't being found.
we found the culprit. i had shared the file via facebook chat, and it had clipped the tilde off the file name.
seems to be working now!
cheers Matt
On Wed, Feb 10, 2016 at 7:57 PM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
On 2016-02-10 10:24, i go bananas wrote:
i just made my first proper external, and was so super chuffed that i got it working.
i'm on osx, so using .pd_darwin extension.
i put it in my extra folder, made a demo patch in pd, and it works fine.
only problem is, when i shared the .pd_darwin with 2 friends, it didn't work for either of them. (i checked they had put it in the extra folder)
does anyone have an idea what might be wrong?
how about:
tell them to Pd in verbose-mode ("-verbose"), and see whether the external can be found (and if it can't be found, this will give you a clue where Pd searches for the libraries).
if it can be found, try to find out whether the dylib loader throws an error (e.g. on the stderr/stdout; so you might need to start Pd from the cmdline).
do you use the same Pd version? Pd's API is very stable, but every now and then a new function is added. if you use such a new function in your code, then you cannot use the external with a version of Pd that predates the introduction of said function).
do you (dynamically) link against non-standard libraries? are they present (and in a searched-for location) on your friends machine?
fgmasdr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
i go bananas -
IOhannes m zmoelnig