Bugs item #3164892, was opened at 2011-01-24 19:20 Message generated for change (Tracker Item Submitted) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3164892...

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: externals Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: IOhannes m zmlnig (zmoelnig) Assigned to: Hans-Christoph Steiner (eighthave) Summary: template/Makefile should allow to point to Pd-source

Initial Comment: the template/Makefile (1.0.7 as of rev.14811) currently assumes that it knows approximately where i have my Pd-sources installed. unfortunately it does not.

there is no direct way to specify the full path to all Pd-includes. instead, there is a PD_INCLUDE variable, but for unknown reasons, this will get a "/pd" suffixed.

this is bad, because: - it will only work with installed versions of Pd (no way to specify the path to the currently used Pd-sources) - it will only work with the yet-unreleased Pd-0.43 and above - it won't work with the Pd-extended installs (as these need a "/pdextended" suffix), at least not if the user doesn not feel like juggling with symlinks

i suggest to: - allow a single variable to point directly to the sources (either use PD_INCLUDE for that, or chose PD_SRC, which seems to have been a common standard in a lot of Makefiles before) - provide defaults that still provide the old behaviour (e.g. use "PD_INCLUDE=$(PD_PATH)/include/pd"

in general i would suggest to: - never append path to a variable that cannot be overridden, instead provide a separate variable with the appended path (introduce "PD_BIN=$(PD_PATH)/bin/pd" rather than use $(PD_PATH)/bin/pd anywhere directly)

----------------------------------------------------------------------

You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3164892...