No worries! It's one of those things that confused many people coming from Pd extended where [declare] didn't exist yet *) and even large libraries like "zexy" or "iemlib" were shipped as one binary per object class.
Christof
*) they had [import], which I think served a similar purpose.
On 07.01.2021 01:37, Allister Sinclair wrote:
I'm pretty sure the problem you're seeing is that recent versions of zexy and iemlib are
built as a single binary (zexy.pd_linux, iemlib.pd_linux) instead of individual binaries for each object class
Oh ok I didn't know that, I was going bonkers, I never took the time to understand all this before
You can either add them to the start up libraries ("File->Startup...->New...") or load
them explicitly by putting a [declare -lib zexy -lib iemlib] in your patch.
Indeed it works now. I feel a bit stupid. Since the other libraries didn't require that I thought the problem was elsewhere
Thank you for your time!
Allister
Le jeu. 7 janv. 2021 à 01:07, Christof Ressi <info@christofressi.com mailto:info@christofressi.com> a écrit :
Actually, I checked the zexy folder and found that the externals aren't built, nothing, all I see is the .pd help files, same for iemlib, no wonder pd wont find them. On the other hand other libraries such as 'ggee' installed fine. Tried again installing from Deken, but no luck.I'm pretty sure the problem you're seeing is that recent versions of zexy and iemlib are built as a single binary (zexy.pd_linux, iemlib.pd_linux) instead of individual binaries for each object class. This means you have to load the libraries before you can create any objects. You can either add them to the start up libraries ("File->Startup...->New...") or load them explicitly by putting a [declare -lib zexy -lib iemlib] in your patch. Christof On 06.01.2021 23:24, Allister Sinclair wrote:thanks for responding, Actually, I checked the zexy folder and found that the externals aren't built, nothing, all I see is the .pd help files, same for iemlib, no wonder pd wont find them. On the other hand other libraries such as 'ggee' installed fine. Tried again installing from Deken, but no luck. Tried downloading zexy from https://puredata.info/downloads/zexy <https://puredata.info/downloads/zexy> and compiling myself, same thing happens (nothing but the .pd help files) Don't know what's going on > i take this as a hint that before, you used to run Pd from the > "puredata" package that ships with Ubuntu Studio. correct? Correct > what is "it"? > when does it say that? when I click on a library in the "find externals" window, a popup window asks if I want to install in the /home/allister/.local/lib/pd/extra, if I say no and browse another directory, that's when I get the error message Le mer. 6 janv. 2021 à 20:54, IOhannes m zmölnig <zmoelnig@iem.at <mailto:zmoelnig@iem.at>> a écrit : On 1/6/21 7:38 PM, Allister Sinclair wrote: > Dear pd list, > > I have compiled and installed pd Pd 0.51.4 on Ubuntu Studio > and some major libraries that I have reinstalled via deken no lonork, > like zexy and iemlib. I tried with and without adding the path. > > It worked fine before on the same machine same os > > my externals are located in my home folder at > /home/allister/.local/lib/pd/extra > could that be a problem? no. Pd will automatically search this path. > externals used to be in /usr/lib/pd/extra/, but deken will only install > stuff in > /home/allister/.local/lib/pd/extra now i doubt that deken ever installed into /usr/lib/pd/extra on your system (you *can* make it do that, but it's not very wise). /usr/lib/pd/extra/ is the place where your package manager ("apt-get") will install external Pd-libraries into. i take this as a hint that before, you used to run Pd from the "puredata" package that ships with Ubuntu Studio. correct? > it says: bad option ".externals_searchui": must be -default, -detail, > -icon, -message, -parent, -title, or -type what is "it"? when does it say that? > > Or could it be an incompatibility of the libraries with the latest version > of pd? > no. very unlikely. (unless you accidentally switched architectures when compiling Pd yourself.) Pd itself is famous for keeping binary compatibility. i'm pretty sure you can still load binaries that were compiled twenty years ago. anyhow: first thing to check is, whether Pd can actually find the externals (despite of what i said above). start Pd with "-verbose" to see how it searches and what it finds. raise the debug-level in the Pd-console to "4 all" to see more messages. start Pd from the cmdline to see any additional messages. search those additional messages for information on *why* a library could not be loaded. gfmsar IOhannes PS: Debian/bullseye and Ubuntu/hirsute ship with Pd>=0.51-4 _______________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list <https://lists.puredata.info/listinfo/pd-list> -- Allister Sinclair _______________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list UNSUBSCRIBE and account-management ->https://lists.puredata.info/listinfo/pd-list <https://lists.puredata.info/listinfo/pd-list>_______________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list <https://lists.puredata.info/listinfo/pd-list>-- Allister Sinclair
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list