Well my worries are this: I made a abs that uses [some~] which calls 3thpty pthread. I want the abs to be opened with all OS. I`m using Deken as source of [some~] so in my abs I [declare] a folder where I put: some~.dll pthread.dll some~.pd_darwin ? pthread ? some~.l_i386? pthread ? some~.pd_linux? pthread ? And there, just work. I know that I can do this with objects that DONT need pthread. How do I handle 3th pty Libs if those *are not* in the Deken Pkg?
Mensaje telepatico asistido por maquinas.
To: pd-list@lists.iem.at From: zmoelnig@iem.at Date: Wed, 20 Jul 2016 17:07:44 +0200 Subject: Re: [PD] Deken and Dependencies
On 07/20/2016 04:23 PM, Lucas Cordiviola wrote:
What will be the problem for a linux system to look for the 3th party Lib in the same folder as the ext (which needs it) if it can't find anywhere else in the local system?
IYO this is adding cruft?
yes.
We are discussing Deken dependencies and abs sharing.
thanks for the reminder :-)
And also I`m following *your* good idea that a deken pkg must be “self operational”.
yes.
Lets have the “normal ubuntu” users a more practical way of Pd while “super users” like you can do all the “$ sudo apt-get install pd-deken-apt” thing.
i think you misunderstood that (most likely because you are not using linux). the idea is, that anybody who installed "puredata" (the core Pd-vanilla package distributed on Debian and derivatives), also has "pd-deken-apt" installed (automatically). there is nothing "super user" to that.
gsmdr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list