the help patch of declare says -stdpath is relative to Pd. this does not necessarily mean it has to be the pd binary, it could mean, the Pd root directory, which would be the folder that contains bin and extra. but certainly not relative to the extra directory of pd.
I think -stdpath extra/somedir is the way to go. but without the "../". (maybe that is only because I am used to it from mac.) but I also think people will want to include things that are not necessarily in extra.
marius.
Hans-Christoph Steiner wrote:
On GNU/Linux and Windows, -stdpath work like this: [declare - stdpath ../extra/<somedir>]. On Mac OS X, you need to omit the "../", i.e. [declare -stdpath extra/<somedir>]. Since that means that [declare] with -stdpath has broken behavior, I want to suggest a change that would make it more intuitive but would break on all platforms:
Right now, I don't see any reason why -stdpath should include the "../ extra" part. Since all externals have been included in "pd/extra" by convention for a long time, it seems to me that it would make the most sense to make -stdpath relative to "/path/to/pd/extra". (I remember many years ago some people using an 'externs' folder, but I haven't seen/heard that in years). This would make the above [declare] like this:
[declare -stdpath <somedir>]
I think the same would apply to -stdlib:
[declare -stdlib <somedir>]
.hc
I have the audacity to believe that peoples everywhere can have three meals a day for their bodies, education and culture for their minds, and dignity, equality and freedom for their spirits. - Martin Luther King, Jr.
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev