Bugs item #2933376, was opened at 2010-01-16 13:14 Message generated for change (Comment added) made by reduzent You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2933376...
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: [pd-gui-rewrite] [declare -stdpath] expands relative to patc
Initial Comment: It seems, that a [declare -stdpath] of pd-gui-rewrite expands the search pathes relative to the patch's location instead of relative to pd's installation location.
----------------------------------------------------------------------
Comment By: Roman Haefeli (reduzent) Date: 2010-01-17 11:06
Message: sorry, couldn't figure out how to attach a file. here's the patch declare_-stdpath_pd-gui-rewrite_bug.pd :
#N canvas 309 548 453 272 10; #X declare -stdpath extra/ext13; #X obj 6 55 wavinfo; #X obj 7 10 declare -stdpath extra/ext13; #X text 68 38 <- loads in pd < pd-gui-rewrite , if 'ext13' is installed to <pd-location>/extra; #X text 66 75 <- does not load in pd-gui-rewrite , since the -stdpath does not search relative to the pd installation location (i.e. <pd-gui-rewrite-location>) , but relative to the (i.e. this) patch's location.;
----------------------------------------------------------------------
Comment By: Roman Haefeli (reduzent) Date: 2010-01-17 11:03
Message: I don't quite see how a patch can help debug the problem, since a patch containing any
[declare -stdpath <libdir-name>] [<object_from_libdir>]
would expose the problem. More critical is the location of the patch, since - as I already said - the flag -stdpath seems to expand the searchpath relative to the patch's path instead of relative to pd-gui-rewrite's install location.
Anyway, I attach the patch.
And here the -verbose output, when patch is located in /home/roman:
tried /home/roman/declare_-stdpath_pd-gui-rewrite_bug.pd and succeeded tried /home/roman/../extra/ext13/wavinfo.l_i386 and failed tried /home/roman/wavinfo.l_i386 and failed tried ../extra/wavinfo.l_i386 and failed tried /home/roman/../extra/ext13/wavinfo.pd_linux and failed tried /home/roman/wavinfo.pd_linux and failed tried ../extra/wavinfo.pd_linux and failed tried /home/roman/../extra/ext13/wavinfo/wavinfo.l_i386 and failed tried /home/roman/wavinfo/wavinfo.l_i386 and failed tried ../extra/wavinfo/wavinfo.l_i386 and failed tried /home/roman/../extra/ext13/wavinfo/wavinfo.pd_linux and failed ^ this indicates, that [declare] appends the value from the flag -stdpath to the patch's path '/home/roman' instead of the pd-gui-rewrite's install location, which is in /home/roman/pd-svn/pd-gui-rewrite/
tried /home/roman/wavinfo/wavinfo.pd_linux and failed tried ../extra/wavinfo/wavinfo.pd_linux and failed tried /home/roman/../extra/ext13/wavinfo.pd and failed tried /home/roman/wavinfo.pd and failed tried ../extra/wavinfo.pd and failed tried /home/roman/../extra/ext13/wavinfo.pat and failed tried /home/roman/wavinfo.pat and failed tried ../extra/wavinfo.pat and failed wavinfo ... couldn't create
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave) Date: 2010-01-17 01:52
Message:
An example patch is always very helpful, especially if it triggers the problem every time that it is run. Ideally the example patch would have only enough objects to cause the problem, but nothing else.
----------------------------------------------------------------------
You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2933376...