On 04/26/2011 03:42 PM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-04-26 15:23, yvan volochine wrote:
salut Matthieu
another question:
is there a way to force gridflow external to load from a specified path?
ie: I'm trying to setup pd-vanilla wth gridflow-9.13 where the user already has pd-extended with gridflow-9.12.
(don't ask me why =)
gridflow.pd_linux (9.12) is in ~/pd-externals/gridflow gridflow.pd_linux (9.13) is in ~/pd-vanilla-externals/gridflow-9.13
problem is that pd -lib gridflow (with the new path to 9.13) still loads the one from pd-externals (9.12) although ~/pd-externals/gridflow is *not* in his path.
is there any workaround to this ?
~/pd-externals/ is _always_ in the path. you might be able to turn this off, by specifying "-nostdpath", though this will also turn off searching of .../pd/extra/
anyhow, if you add ~/pd-vanilla-externals/gridflow-9.13 to your search paths (e.g. using the "-path" flag) , then the gridflow found therein should take precedence over the one in ~/pd-externals/
I see.. I find this weird that this does not work if gridflow-9.13 is in my path in .pdsettings) but it does with pd -path xxx
also, `pd -path /path/to/gridflow-9.13' gives me: "GridFlow 9.13... GridFlow was compiled on Apr. 26 2011 [snip] /path/to/griflow-9.12/gridflow_x11.pd_linux undefined symbol... /path/to/griflow-9.12/gridflow_gem_loader.pd_linux undefined symbol... /path/to/griflow-9.12/gridflow_pdp.pd_linux undefined symbol... "
so I guess there is no workaround except removing 9.12 from pd-externals..
cheers, _y