Hi,
yes, it fixes the problem.
I haven't used Pd heavily in recent times,
and wasn't aware of the [declare] thing (and I guess my general expectation
was that something installed by a package manager is available right away
without any further interaction).
But now, if someone asks me why stuff installed with deken isn't available
I at least know the answer :)
If you still have questions, check manual's section 4 (externals), I recommend as you will also find other answers and more details about this
Best,
Niklas
Antoine Rousseau wrote on 12.02.2020 13:41 (GMT +01:00):
>
>
> Hi,
>
>
> the best way IMO is to add a declaration into the patch which is using the
> library.
>
> E.g use [declare -path ggee]
>
>
> If this doesn't fix your problem please give use a more detailed
> description (OS, Pd version, what external you try to load, which paths
> are declared in configuration etc...).
>
>
> Le mer. 12 févr. 2020 à 10:19, <nik@parkellipsen.de
> <mailto:nik@parkellipsen.de> > a écrit :
>
>> Hi,
>>
>> whenever installing a package with deken, I still have to add the path
>> manually for the extensions to be found.
>>
>> The base path is present, but the package paths are not.
>>
>> Is this the expected behaviour ? If not, is there a setting
>> so that the installed packages are found automatically ?
>>
>> Best,
>> Niklas
>>
>>
>> _______________________________________________
>> Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing
>> list
>> UNSUBSCRIBE and account-management ->
>> https://lists.puredata.info/listinfo/pd-list
>
>
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list