I have just received my multichannel bela mini kit 🙂

BUT, when i try to run my code, I get the following message:

 ____  _____ _        _
| __ )| ____| |      / \
|  _ \|  _| | |     / _ \
| |_) | |___| |___ / ___ \
|____/|_____|_____/_/   \_\

The platform for ultra-low latency audio and sensor processing

http://bela.io

Bela image, v0.3.8f,  4 January 2022

More info at https://github.com/BelaPlatform/bela-image-builder/releases

Built with bela-image-builder master@f7d3b8d11dc3b7b89ee4be9b1ec94eefcf22524f
on Tue Jan  4 02:28:17 UTC 2022

root@bela:~# ./Bela/projects/Gloves/Gloves
./Bela/projects/Gloves/Gloves: error while loading shared libraries: libseasocks.so.1.4.3: cannot open shared object file: No such file or directory

I think it is something with my cross compilation stuff - it's a fork of xcBela with some addons specific to my project

How did you build the project? With you cross-compiling toolchain? I think this version of the image has a newer version of libseasocks so you'll need to make sure you link against the new one. Similarly, a binary that was built for an older board will need to be relinked in order to run on the new image. If you copied the project(s) from a previous version of the board, you just need to rebuild. Using RELINK=1 at the Makefile would force a relink.

    giuliomoro Yes with cross compiling toolchain... I think I just need to update the local sysroot files.. but the toolchain rely on make libbelafull
    but now I get make: *** No rule to make target 'libbelafull'. Stop.

        I'm not sure I understand... I have Bela as a submodule, and I already moved to the newest commit in dev branch.... can you explain in a bit more detail ?

        How did you provide the make libbelafull functionality? Was that through a commit you had on top of the master or dev branch? Or was it a set of uncommitted changes to the Makefile in your working folder? Or was it via a CustomMakefileBottom.in file?
        In the first case you'll need to git cherry-pick that commit on top of the current dev.
        In the second case you need to reapply those changes after updating.
        In the third case you probably don't need to make any changes and make libbelafull should still work.

        Additionally, keep in mind that libseasocks is provided on the image, so updating the core code that you use to build is not going to help you with the libseasocks issue: You also need to update the libseasocks that is available on your sysroot.

        I forgot that I needed to make the libbelafull target in CustomMakefileBottom.in...
        Now it compiles and runs, but I get errors with OscSender that I have not seen before ?

        AuxTaskNonRT OscSenderTask_192.168.0.1008110: could not open pipe /proc/xenomai/registry/rtipc/xddp/p_OscSenderTask_192.168.0.1008110: (2) No such file or directory
Aborting AuxTaskNonRT OscSenderTask_192.168.0.1008110
AuxTaskNonRT OscSenderTask_192.168.0.1009110: could not open pipe /proc/xenomai/registry/rtipc/xddp/p_OscSenderTask_192.168.0.1009110: (2) No such file or directory
Aborting AuxTaskNonRT OscSenderTask_192.168.0.1009110
AuxTaskNonRT OscSenderTask_192.168.0.1117111: could not open pipe /proc/xenomai/registry/rtipc/xddp/p_OscSenderTask_192.168.0.1117111: (2) No such file or directory
Aborting AuxTaskNonRT OscSenderTask_192.168.0.1117111
AuxTaskNonRT OscSenderTask_192.168.0.1127112: could not open pipe /proc/xenomai/registry/rtipc/xddp/p_OscSenderTask_192.168.0.1127112: (2) No such file or directory
Aborting AuxTaskNonRT OscSenderTask_192.168.0.1127112
AuxTaskNonRT OscSenderTask_192.168.0.1137113: could not open pipe /proc/xenomai/registry/rtipc/xddp/p_OscSenderTask_192.168.0.1137113: (2) No such file or directory
Aborting AuxTaskNonRT OscSenderTask_192.168.0.1137113
AuxTaskNonRT OscSenderTask_192.168.0.1147114: could not open pipe /proc/xenomai/registry/rtipc/xddp/p_OscSenderTask_192.168.0.1147114: (2) No such file or directory
Aborting AuxTaskNonRT OscSenderTask_192.168.0.1147114
AuxTaskNonRT OscSenderTask_192.168.0.1157115: could not open pipe /proc/xenomai/registry/rtipc/xddp/p_OscSenderTask_192.168.0.1157115: (2) No such file or directory
Aborting AuxTaskNonRT OscSenderTask_192.168.0.1157115
AuxTaskNonRT OscSenderTask_192.168.0.1167116: could not open pipe /proc/xenomai/registry/rtipc/xddp/p_OscSenderTask_192.168.0.1167116: (2) No such file or directory
Aborting AuxTaskNonRT OscSenderTask_192.168.0.1167116
AuxTaskNonRT OscSenderTask_192.168.0.1177117: could not open pipe /proc/xenomai/registry/rtipc/xddp/p_OscSenderTask_192.168.0.1177117: (2) No such file or directory
Aborting AuxTaskNonRT OscSenderTask_192.168.0.1177117
AuxTaskNonRT OscSenderTask_192.168.0.1317131: could not open pipe /proc/xenomai/registry/rtipc/xddp/p_OscSenderTask_192.168.0.1317131: (2) No such file or directory
Aborting AuxTaskNonRT OscSenderTask_192.168.0.1317131
AuxTaskNonRT OscSenderTask_192.168.0.1327132: could not open pipe /proc/xenomai/registry/rtipc/xddp/p_OscSenderTask_192.168.0.1327132: (2) No such file or directory
Aborting AuxTaskNonRT OscSenderTask_192.168.0.1327132
AuxTaskNonRT OscSenderTask_192.168.0.1058000: could not open pipe /proc/xenomai/registry/rtipc/xddp/p_OscSenderTask_192.168.0.1058000: (2) No such file or directory
Aborting AuxTaskNonRT OscSenderTask_192.168.0.1058000

        I'm on the tip commit of origin master:
        b6491178b859eb8977f494eb9ba4806920eea4b0

        It turns out that the AuxTaskNonRT name was too long ?
        I have seen this before, so I tried making it shorter and the error went away...
        It seems to pop up a bit at random :S

        I did the name change from:

        std::string("OscSenderTask_") + ip_address + std::to_string(port)

        to

        std::string("OscSndTsk_") + ip_address + std::to_string(port)

        and the problem was gone. Also fixed a missing include of <string> but I think you also did that on dev branch ?