But immediately afterwards I found that iemmatrix, moocow, and tof weren't found by Pd.... Looking in the package contents, I them and added them to the path.

So I have two SIMPLE questions:

1. Why aren't all of the Pd extensions being loaded at startup?

2. When adding extensions to the path, why won't "/Applications/Pd-extended.app/Contents/Resources/extras" load everything? I had to add the missing libraries one at a time.

2. Similar reason to the one above, I guess. I assume you mean the subfolders. You can still access them without adding them all to the path. You can use [declare] for paths and [import] for libraries. Also, you can add the folder name in the external, like [zexy/wrap], which will not only load the external but will force Pd to use zexy's and not vanilla's. Doing all that also self-documents the patch, which is another reason why I don't think it's all that bad to not load libraries on startup by default.

All that's just speculation, though. I don't actually know the real answers to your questions .

Can an admin please let him know this as well?

sorry, but could you please explain how I might use [declare]?

If I make a patch with just [declare -path "path/external/subdirectory"] and put it inside an external's folder, will that load the subdirectory's objects as well? The help file for [declare] also has a confusing warning about putting [declare] in abstractions.

Thanks

i'm having several problems with the externals i'm trying to use.

First of all, I'm trying to add an external to print "hello world" on the screen. I copied the source from the "my first external tutorial" and everything compiled correctly. I added the ~.pd_linux and the ~.o on the /usr/lib/pd-extended/extra/helloworld directory.

In file->path... I put the /usr/lib/pd-extended/extra/helloworld. And in Startup... added external. My files are named external.pd_linux and external.o.

Once I have changed the path and startup settings the startup text box started showng the following messages:

  [import] $Revision: 1.2 $
    [import] is still in development, the interface could change!
    compiled against Pd version 0.42.5
tried but couldn't sync A/D/A
libdir: can't load library
Gem: can't load library
cyclone: can't load library
zexy: can't load library
creb: can't load library
cxc: can't load library
iemlib: can't load library
list-abs: can't load library
mapping: can't load library
markex: can't load library
maxlib: can't load library
memento: can't load library
mjlib: can't load library
motex: can't load library
oscx: can't load library
pddp: can't load library
pdogg: can't load library
pixeltango: can't load library
pmpd: can't load library
rradical: can't load library
sigpack: can't load library
smlib: can't load library
toxy: can't load library
unauthorized: can't load library
pan: can't load library
hcs: can't load library
jmmmp: can't load library
ext13: can't load library
ggee: can't load library
flib: can't load library
ekext: can't load library
flatspace: can't load library
pdp: can't load library
pidip: can't load library
load_object: Symbol "external_setup" not found
external: can't load library

Does anyone know what I did wrong?

A last question. Once I got the library installed correctly, could I simply cal the method "helloworld_setup", on an pd object to print my message?

Thanks for helping!

But i still don't understand how to use an external. I've already put the binaries on the right directory(i think), and set the paths and startup binaries.

What have i missed?

So you have the class built alright, but what exactly happens when you try to instantiate it in Pd? After you type 'helloworld' in an object box? Do you see red lines around it? What error message in the Pd console? Or, if it does instantiate, what happens when you send a bang into it?

Katja

in the PD-extended initiation

load_object: Symbol "helloworld_setup" not found
helloworld: can't load library

what could it be?

/usr/lib/pd-extended/extra

So, not with the file name included. Read this:

http://en.flossmanuals.net/pure-data/ch011_advanced-configuration

Then, restart Pd and instantiate a helloworld object. The symbol should be found. If not, run command nm on the binary to check which symbols are exported. Should look like this:

/Applications/Pd-extended.app/Contents/Resources/extra/katja/helloworld.pd_darwin(single module):
00000f34 t __dyld_func_lookup
00000000 t __mh_dylib_header
U _class_addbang
U _class_new
U _gensym
00000f42 T _helloworld_bang
0000100c b _helloworld_class
00000f5a T _helloworld_new
00000f7b T _helloworld_setup
U _pd_new
U _post
00000f20 t dyld_stub_binding_helper

Katja

00000068 T _Z14helloworld_newv
00000084 T _Z15helloworld_bangP11_helloworld
00000000 T _Z16helloworld_setupv
         U __gxx_personality_v0
         U class_addbang
         U class_new
         U gensym
00000000 b helloworld_class
         U pd_new
         U post

and the same errors occurs.

load_object: Symbol "helloworld_setup" not found
helloworld: can't load library

http://puredata.hurleur.com/sujet-5535-external-development-shader

Katja

ld: helloworld.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC
helloworld.o: could not read symbols: Bad value

and now this new message ocurrs when mounting the .pd_linux.

U class_addbang
U class_new
U gensym
0000000000000000 T helloworld_bang
0000000000000000 b helloworld_class
000000000000001d T helloworld_new
000000000000003e T helloworld_setup
U pd_new
U post

My binary is like that now.

Did anyone have this same problem?

Thx