location of pd.dll when cross-compiling

[grame-cncm]

location of pd.dll when cross-compiling

[sletz]

So if "other distros may vary" what are we supposed to do? Is there any real generic location that would be more appropriate?

[umlaeute]

no, I don't think that there is a generic installation directory for w32 dlls on linux systems (which is fair enough: there isn't even a generic installation directory for w32 dlls on windows systems).

however, there are a few places which I think are definitely wrong, and /usr/include is quite on top of this list.

• use a directory that is not in contradiction to the Filesytem Hierarchy Standard
• possibly use a directory that matches the location of other dlls on your linux system.
• make it configurable (either via some configuration file or via an environment variable, or both)

[umlaeute]

so here's a suggestion:

• use a PDBINPATH (or FAUST_PDBINPATH) variable
• use a sane default value like /usr/lib/i686-w64-mingw32/pd/
• have faust2w32puredata include faustpath (after setting the variable to the default value; before using it)
• have faustpath include optional configuration files: /etc/faust/defaults and ~/.faust/defaults (if you allow both system-wide and per-user config, allow the per-user configuration to override the system-wide config, by including it later)
• in these config-files you (and any potential user of faust2w32puredata) can adjust the actual installation path to match their system (and distribution packagers might provide defaults in the system-wide config that matches the distribution expectations.
• rinse and repeat for other cross-compilation targets

[sletz]

Thanks but well... either you can can send us a patch to do all this stuff, or just forget packaging this faust2w32puredata script...

[umlaeute]

i'll come up with a patch...