If we separate the externals into repos with a standardized Makefile, I imagine they should build fine for both vanilla and l2ork. I see overlap here that’s more advantageous then having all the former Pd-extended externals being maintained on Sourceforge and updated on Github for l2ork.
Again, hate to sound like a broken record, but I’d spearhead this effort as soon as I get time again in a few weeks. -------- Dan Wilcox @danomatika danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/> > On Dec 20, 2014, at 5:17 PM, [email protected] wrote: > > >> FWIW, a good chunk of this cleanup is currently taking place in pd-l2ork. > >> Namely, we are looking for redundant objects which are then disabled and > >> replaced by legacy abstractions where possible or linked to other objects > >> with identical or near identical functionality (again, where possible); we > >> are disabling problematic objects that have design issues (e.g. foxy and > >> flatspace IIRC), as well as looking to replace those with new objects that > >> provide said functionality the right way. Finally, we are looking to > >> standardize documentation (e.g. pd-l2ork has documentation for the entire > >> cyclone adapted to the pddp format). If anyone desires git access to > >> assist with this, please let us know.
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
