You can do that now, just put the libs and abstractions in the same folder as the patches.
Pd looks in the local path of the patch as well as the system & user specified locations, plus you can use [declare] as well: > On Jul 27, 2017, at 10:53 PM, pd-list-requ...@lists.iem.at wrote: > > From: Federico Camara Halac <camaraf...@gmail.com > <mailto:camaraf...@gmail.com>> > Subject: Re: [PD] Easy way to list used abstractions in patch? > Date: July 27, 2017 at 10:51:49 PM GMT+2 > To: Matt Davey <hard....@gmail.com <mailto:hard....@gmail.com>> > Cc: "pd-list@lists.iem.at <mailto:pd-list@lists.iem.at>" > <pd-list@lists.iem.at <mailto:pd-list@lists.iem.at>>, jlistshit > <jlists...@kliklak.net <mailto:jlists...@kliklak.net>> > > > Well I don't know about how extended worked, since I really never used it. I > only mean to 'export' into a pd distrib that is only intended to use with a > particular patch that only has the requirements of that patch > > if you could do that, then you could just autogenerate pd-extended, no? -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
