[PD-dev] hex characters in library names

Roman Haefeli reduzierer at yahoo.de
Sat Jun 12 10:16:51 CEST 2010


On Wed, 2010-04-14 at 10:12 +0200, IOhannes m zmoelnig wrote:
> 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)

Thanks for the help. Actually the main work was already done by Georg
Holzmann. Only very few were missing (probably new classes?). Of course,
I initially tried one of those, which made me assume, there is no
hexloader support in iemmatrix.

I submitted a patch to tracker. Hopefully this fixes all aliases.

Roman




More information about the Pd-dev mailing list