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
signature.asc
Description: OpenPGP digital signature
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
