On 2010-04-14 00:19, Roman Haefeli wrote:
If it is only a matter of someone doing the boring uninspiring uninteresting painful work of renaming those functions, I _might_ be able to help, if there is interest (IOhannes?). If so, I would probably need some advice on how to do it correctly.
run Pd in verbose mode and load hexloader. try to instantiate [mtx_*~] and watch out for the exact name of the setup fun. create a stub function of that very name that points to the real setup function (look at "iemtx_mul__setup()" for how this is done)
obviously this could be done in a more intelligent way, by manually calculating the setup-function name.
also be sure to add stubs for the hexloader built into Pd whenever they differ (just repeat the above without hexloader loaded, and see what's going on; you probably need to provide dummy libs like "mtx_*~.pd_linux" in order to see the requested name) IIRC, the hexloader built-into Pd does everything but filename-mangling; therefore you still need the "hexloader" lib in order to load libraries with "illegal" filenames (e.g. you cannot have a file named "mtx_>.dll" on an NTFS/FAT32 filesystem)
fgmasr IOhannes
Roman
On Sun, 2010-04-11 at 16:36 -0400, Lee Azzarello wrote:
I'm trying to load an object named [mtx_*~]
I have the proper load path installed. I can load other objects in the same directory. If I look for the library in that directory (/usr/lib/pd/extra/iemmatrix), I find a file named mtx_0x2a0x7e.pd_linux. The hex translates to *~ in ASCII. So this should be the proper library to load for the [mtx_*~] object, right?
I'm unaware of how to debug this since it looks like I'm doing things right.
-lee
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev