#Can't build OrcaSlicer 2.1.1 on Raspberry Pi 5/RasPi OS (Bookworm 12)

1 messages · Page 1 of 1 (latest)

strange venture
#

Hello.
I had no problem to build OrcaSlicer 2.0.0 on my Raspberry Pi 5 (running official Raspberry Pi OS Bookworm 12) even if it took quite a long time and even if the ninja builder was new.
Unfortunately, I face an issue trying to build OrcaSlicer 2.1.1 and there is not so much error log. Here is what I get:

In file included from /home/aqua/Softwares/OrcaSlicer/src/slic3r/GUI/ConfigWizard.hpp:8,
from /home/aqua/Softwares/OrcaSlicer/src/slic3r/GUI/GUI_App.hpp:14:
/home/aqua/Softwares/OrcaSlicer/src/slic3r/GUI/GUI_Utils.hpp: At global scope:
/home/aqua/Softwares/OrcaSlicer/src/slic3r/GUI/GUI_Utils.hpp:43:18: warning: ‘Slic3r::ColorRGBA Slic3r::GUI::decode_color_to_float_array(std::string)’ defined but not used [-Wunused-function]
43 | static ColorRGBA decode_color_to_float_array(const std::string color)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
[264/469] Building CXX object src/libslic3r/CMakeFiles/libslic3r.dir/OpenVDBUtils.cpp.o
ninja: build stopped: subcommand failed.

I have no idea of which subcommand failed and why… Does anyone faced something similar and has a hint (to solve the problem or to get more verboose error mesage)? I ran "./BuildLinux -dsir" to try to build…
Thank you :)!

PS: I guess it represents more work but it should be great if the OrcaSlicer building team was able to include an arm64 architecture AppImage in addition to the x86_64 such as it's done for MAC OS!

shrewd onyx
#

Search the build output for the “error” command. The above is a warning and the error you’re seeing usually means something upstream failed but you don’t see it in the immediate vicinity of the output because of the parallel build producing intertwined log outputs. You can pipe the outcome of the build to a file and search in there

strange venture
#

Hello igiannakas. Thank you for your quick reply. I am going to follow your advice. I'll try to find the build output or to pipe the output of the build to a file. Is it something like that: ./BuildLinux -dsir > "build_log.txt"?

shrewd onyx
#

Yeap correct

strange venture
#

OK thanks. I go back to the Pi right now and I try!

strange venture
#

I was finally able to build Orca 2.1.1! Thank you.

#

I have a "naive" question. This afternoon I try to build the 2.2.0-beta release of OrcaSlicer on my Raspberry Pi from the tar.gz source file. I had a lot of errors I was not able to manage. Then, I git clone the repository, and I had no problem to build this new version of Orcaslicer. What difference between the tar.gz file and the git clone can explain the build problem? It is just by curiosity. Thank!