<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""><div class=""><div class="">
--------<br class="">Dan Wilcox<br class="">@danomatika<br class=""><a href="http://danomatika.com" class="">danomatika.com</a><br class=""><div class=""><a href="http://robotcowboy.com" class="">robotcowboy.com</a></div>
</div>
<div><blockquote type="cite" class=""><div class=""><br class=""><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(127, 127, 127, 1.0);" class=""><b class="">From: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">katja <<a href="mailto:katjavetter@gmail.com" class="">katjavetter@gmail.com</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(127, 127, 127, 1.0);" class=""><b class="">To: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">pddev <<a href="mailto:pd-dev@iem.at" class="">pd-dev@iem.at</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(127, 127, 127, 1.0);" class=""><b class="">Date: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">March 8, 2015 at 6:52:38 AM EDT<br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(127, 127, 127, 1.0);" class=""><b class="">Subject: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">[PD-dev] Makefile.pdlibbuilder and a question about default install paths</b><br class=""></span></div><br class=""><br class="">Hello,<br class=""><br class="">Currently I am working on a one-size-fits-all build method for Pd<br class="">libs. It is meant to take the template Makefile concept to a next<br class="">level. The template is a great help for building Pd libs but it has a<br class="">few limitations:<br class=""><br class="">1. source and rule definitions are together in a single file so it is<br class="">a pain to upgrade Makefiles to a new template version<br class=""><br class="">2. the template can not handle multiple source files for multiple<br class="">class executables<br class=""><br class="">3. implicit dependencies (headers) aren't checked<br class=""><br class="">Makefile.pdlibbuilder overcomes these limitations. It functions as an<br class="">include in a Makefile which defines sources for classes. For non-clean<br class="">build of target all, Makefile.dependencies is generated. A (re)build<br class="">of individual classes can be forced alternatively.<br class=""><br class="">Makefile.pdlibbuilder is in an early stage of development. I've spent<br class="">much time sorting out the best approach for<br class="">multiple-source-per-executable procedures. This is working fine now.<br class="">By way of test I used the method to compile all tilde classes in<br class="">cyclone, which are all multiple-source. It worked right away without a<br class="">single gcc error. This is promising enough for me to continue the<br class="">effort.<br class=""><br class="">My aim is to make it a user-friendly method for building individual<br class="">libs against any of the 'Pd-flavours', while at the same time<br class="">integrating with Pd-extended's unified build system. There's aspects I<br class="">can't figure out on my own, some due to my lack of knowledge, some<br class="">because they need discussion to make decisions.<br class=""><br class="">My first issue is with the default install path for a Pd lib. In the<br class="">template Makefile it's definition boils down to<br class="">/usr/local/lib/pd-externals/, except for OSX where it is ~/Library/Pd.<br class="">The path is overruled by Pd-extended's central Makefile, but when<br class="">building an isolated lib you get this default (which you can<br class="">eventually overrule yourself). For one thing, I'm not fond of<br class="">Makefiles installing stuff deep in a file system, so I would consider<br class="">issuing a warning message or prompt for such a case. Apart from that,<br class="">the question is to which extent the default makes sense at all. I<br class="">found this overview of standard search paths for Pd externals:<br class=""><br class=""><a href="http://puredata.info/docs/faq/how-do-i-install-externals-and-help-files" class="">http://puredata.info/docs/faq/how-do-i-install-externals-and-help-files</a><br class=""><br class="">Are these search paths valid in 'all Pd flavours' (vanilla, extended, L2Ork)?<br class=""><br class="">By the way I don't want to clutter Pd-dev list with attachments but if<br class="">anyone is interested I'd be happy to send Makefile.pdlibbuilder in<br class="">it's current pre-pre-alpha state.<br class=""><br class="">Katja<br class=""></div></blockquote></div><br class=""></div></div></body></html>