i cleaned up the template Makefile (externals/template/Makefile) a bit.
namely i switched to using $@, $< and $^, which makes a lot of things
way more elegant.
other cleanups:
removed the SOURCES_android since this is not used anywhere and is
misleading
use PD_PATH where appropriate
added SOURCES_LIB for .c files holding shared functions
use HELPPATCHES to enumerate -help.pd (usually this info is gathered
automatically; the average user will never see that)
these changes should make zero difference to the user experience of the
templ Makefile.
remaining questions:
DIST PATH:
why does the makefile enforce the manual and examples to be examples/
resp. manual/ folders _in the source directory_ ?
i understand that they should be laid out standardized in the install
directory, but why in the source folder?
why not just:
MANUAL = doc/manual.pdf manuals/anothermanual.pd
and install that into .../$(LIBRARY_NAME)/manual/
INSTALL PATH
why the heck is the default installation path: $(libdir)/pd-externals ??
i cannot remember that this was agreed on by anybody but hans.
i do remember that ~/pd-externals was discussed (and i still would
prefer ~/.pd/extra/ over this unnecessary homedirectory cluttering), but
$(libdir)/pd-externals is news to me.
instead i do remember, that $(libdir)/pd/extra was meant to be the
canonical name for all flavours of Pd (e.g. with PdX and pd-vanilla, in
debian pd-vanilla would look into both /usr/lib/puredata/extra and
/usr/lib/pd/extra, whereas PdX would look into
/usr/lib/pd-extended/extra and /usr/lib/pd/extra (in this order))
i also find, that a related patch has made it into puredata.git.
unfortunately, it is inconsinstent with the template Makefile, as
puredata.git has hardcoded /usr/local/lib/pd-externals/ whereas the tmpl
uses $(libdir)/pd-externals which could well be /usr/lib/pd-externals/
which in turn is never ever searched by Pd.
in case, i haven't said it yet: i don't like this.
,asdr
IOhannes