I see [declare -path fluid~] and ./fluid~ also works
On Thu, 7 Jan 2021 at 14:10 Alexandre Torres Porres <[email protected]> wrote: > > > Em qui., 7 de jan. de 2021 às 14:05, Alexandre Torres Porres < > [email protected]> escreveu: > >> Em qui., 7 de jan. de 2021 às 09:38, alfonso santimone < >> [email protected]> escreveu: >> >>> Works fine here on Win10 64bit. Thanks! >>> Only little thing to watch out is that [ fluid~ ] is the name of another >>> external contained in the (very nice) ceammc library. >>> Obviously calling this by [fluid~/fluid~] just works. >>> >> >> funny, I tested [declare -path fluid~] and that *DOESN'T WORK *if I have >> ceammc in the start up. Meaning it'll just load fluid~ from ceammc. Now, I >> did not expect that... still thinking about it, but it feels like it >> shouldn't be that way. >> > > On the other hand, having [declare -lib fluid~] works by superseding the > priority of 'ceammc' in startup! So I'm using this instead (cause > fluid~/fluid~ just looks terrible!). > > And it seems once you load a binary in startup, it stays there forever and > has priority over search paths. So I need to document this. >
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
