Is there a an easy way to include a bunch of directories recursively, rather than adding each of the 30+ paths available in usr/lib/pd/extra/ alone?
be aware that [declare] and [lib] behavior just changed a bit; they now scan sub-directories of:
- 1 calling patch folder
- 2 paths that you declared in Pd preferences
- 3 standard paths (e.g /usr/lib/pd/extra or ~/.local/lib/pd/extra)
So whatever the way you chose to install "foo" library, i.e whether "foo" folder has been copied locally to the patch, or in "/myHome/myLibs" (provided that you declared "myHome/myLibs" in Pd's path preferences), or in "/usr/lib/pd/extra" (because you used apt-get), all you have to do is put a [declare -path foo] in the calling patch so you can use objects from "foo".
Antoine Rousseau http://www.metalu.net http://metalu.net __ http://www.metaluachahuter.com/ http://www.metaluachahuter.com/compagnies/al1-ant1/
Le dim. 23 sept. 2018 à 21:02, IOhannes m zmölnig zmoelnig@iem.at a écrit :
On 9/23/18 8:27 PM, Atte via Pd-list wrote:
I can think of three ways to make external libraries
(externals/abstractions) available on my debian stable (running pd 0.47.1 from the debian repos):
- install the ones from the debian repos
- using the deken plugin
- compiling by hand
I'd rather stick with one to avoid total mess. What do other debian
users prefer?
with my Debian hat on: the choice should always be to use the Debian repositories, whenever possible. (sometimes this may not be possible, as not all (although most known) Pd-libraries are packaged; or when you need a release of a given library that is newer than Debian/stable).
there is also the "pd-deken-apt" (Debian) package, which allows you to install the Debian packaged libraries from within Pd (using the deken plugin)
gfmdsar IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list