Tox (minimal) compile issue

[lym70]

Hello,

On a Debian Bookworm, after installing required dependencies for targeted build: sudo apt install libtoxcore-dev libncursesw5-dev libconfig-dev libcurl4-openssl-dev python3-dev

I get defines unresolved for TOX_GROUP_MAX_PART_LENGTH and TOX_GROUP_MAX_TOPIC_LENGTH

As well as a few types: Tox_Group_Message_Id, Tox_Group_Exit_Type, Tox_Group_Privacy_State, Tox_Group_Topic_Lock, Tox_Group_Join_Fail, Tox_Group_Mod_Event, Tox_Group_Voice_State.

Build (on PC) was done using: make DISABLE_X11=1 DISABLE_AV=1 DISABLE_SOUND_NOTIFY=1 DISABLE_DESKTOP_NOTIFY=1 ENABLE_PYTHON=1 ENABLE_RELEASE=1

Maybe some minimal libtoxcore version needed?

This was intended as a test before compiling for a headless raspberry, as trying to install repo version would bring some libraries not present on this minimal raspbian install. The aim is to build some group/family mobile notification system for home management on Tox. For this purpose, did not saw what is possible from Toxic python integration? There is also an experimental API build option but did not found any information on this as well.

Thanks&Regards

[lym70]

Well, after getting/building current toxcore (+libsodium-1.0.20 as Debian packages one was also too old), this builds... But for some reason, toxic does not start not finding libraries: toxic toxic: error while loading shared libraries: libtoxcore.so.2: cannot open shared object file: No such file or directory

But they are present/installed correctly: -rwxr-xr-x 1 root staff 516632 17 avril 14:40 libsodium.so.26.2.0 lrwxrwxrwx 1 root staff 19 17 avril 14:40 libsodium.so.26 -> libsodium.so.26.2.0 lrwxrwxrwx 1 root staff 19 17 avril 14:40 libsodium.so -> libsodium.so.26.2.0 -rwxr-xr-x 1 root staff 953 17 avril 14:40 libsodium.la -rw-r--r-- 1 root staff 739058 17 avril 14:40 libsodium.a -rw-r--r-- 1 root staff 1691952 17 avril 14:41 libtoxcore.so.2.21.0 -rw-r--r-- 1 root staff 2173286 17 avril 14:41 libtoxcore.a lrwxrwxrwx 1 root staff 20 17 avril 14:41 libtoxcore.so.2 -> libtoxcore.so.2.21.0 lrwxrwxrwx 1 root staff 15 17 avril 14:41 libtoxcore.so -> libtoxcore.so.2

And /usr/local/lib is in path???

Don't see anything that should prevent finding/loading, access rights looks correct to me... Tell me if you see something wrong there.

FYI, build with experimental API failed but OK without.

[JFreegman]

Have you tried the steps listed at the bottom of the install instructions in the troubleshooting section?

[lym70]

Did not noticed this section from README as I was focusing on INSTALL! Thanks for the hint, ldconfig did the job! Looks python is for adding some toxic embedded scripting, so would not fit my use-case. IYO, does API build may be useful? Did not found some Python/Shell bindings to use toxcore from other programs/scripts, so the idea to see if a CLI app would do the job. There was ratox that looked to fullfill thoses use-cases but looks no more maintained...