[declare -stdpath] doesn't expand any paths (or at least not the expected ones) on Windows.
When using [declare -stdpath extra/osc] in Linux, [packOSC] can be loaded (at least) from the following locations:
/usr/lib/pd/extra/osc
/home/user/pd-externals/osc
When using [declare -stdpath extra/osc] on Windows XP, [packOSC] is not found, while osc is installed in one of those folders:
C:\Documents and Settings\user\Application Data\Pd\osc
C:\Program Files\Common Files\pd\osc
<pd-install-path>\extra\osc</pd-install-path>
However, when Pd is installed in C:\Program Files\pd, this is searched:
C:\Program Files\pd\extra\osc
(but not the other standard paths).
There seems to be no issue with the -stdlib flag. When using [declare -stdlib extra/zexy], zexy objects can be instantiated when zexy is installed in one of those locations:
C:\Documents and Settings\user\Application Data\Pd\zexy
C:\Program Files\Common Files\pd\zexy
<pd-install-path>\extra\zexy</pd-install-path>
Anonymous
Please ignore this section:
"However, when Pd is installed in C:\Program Files\pd, this is searched:
C:\Program Files\pd\extra\osc
(but not the other standard paths)."
I was accidentally using Pd 0.43, that is why I got different results. Pd install path does not matter. Sorry for the noise.
can we close this, now that Pd-0.49 has a revamped search-functionality (and i suggest to use
-pathinstead of-stdpath)?