[Solved] Slicer 2.9.0 flatpak  

RE: Slicer 2.9.0 flatpak

I am on debian trixie as well. I followed the build instructions for PrusaSlicer on github and compiled it from source. No more flatpak shenanigans.

RE: Slicer 2.9.0 flatpak

Thanks for your reply.

I tried this as well but had noch luck, wil try again.

RE: Slicer 2.9.0 flatpak

So, I tried to compile as described ...

CMake Error at libs/accumulators/CMakeLists.txt:15 (target_link_libraries):
  The link interface of target "boost_accumulators" contains:

    Boost::numeric_ublas

  but the target was not found.  Possible reasons include:

    * There is a typo in the target name.
    * A find_package call is missing for an IMPORTED target.
    * An ALIAS target is missing.



-- Generating done (0.3s)
CMake Warning:
  Manually-specified variables were not used by the project:

    CMAKE_DEBUG_POSTFIX


CMake Generate step failed.  Build files cannot be regenerated correctly.
make[2]:  [CMakeFiles/dep_Boost.dir/build.make:92: dep_Boost-prefix/src/dep_Boost-stamp/dep_Boost-configure] Fehler 1
make[1]:  [CMakeFiles/Makefile2:157: CMakeFiles/dep_Boost.dir/all] Fehler 2
make: *** [Makefile:136: all] Fehler 2

no success....

RE: Slicer 2.9.0 flatpak

Did you build the dependencies first? This can take quite a while.

RE: Slicer 2.9.0 flatpak

yes, I followed the description step by step on "Building PrusaSlicer on UNIX/Linux"

CMake Error at /usr/share/cmake-3.30/Modules/FindPackageHandleStandardArgs.cmake:233 (message):
  Could NOT find Boost: Found unsuitable version "1.74.0", but required is at
  least "1.83.0" (found /usr/include, )
Call Stack (most recent call first):
  /usr/share/cmake-3.30/Modules/FindPackageHandleStandardArgs.cmake:601 (_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.30/Modules/FindBoost.cmake:2409 (find_package_handle_standard_args)
  CMakeLists.txt:374 (find_package)

RE: Slicer 2.9.0 flatpak

On your system some more current libboost*-dev libraries are not installed. I think libboost1.83-dev is the current version at the moment. Try to do a "apt update && apt upgrade" or install the libs manually if the -dev versions are not installed.

RE: Slicer 2.9.0 flatpak

I'll check tomorrow.

Thx. 👍 

RE: Slicer 2.9.0 flatpak

Hi, did not work. However, I'll give it another try to compile it.

RE: Slicer 2.9.0 flatpak

The error messages usually helped me find a solution for what was either missing on my system (e.g. some lib<something>-dev packages) or what went wrong and googling helped me on my way.

RE: Slicer 2.9.0 flatpak

OK, so, what I did so far:

followed the Linux howto: https://github.com/prusa3d/PrusaSlicer/blob/master/doc/How%20to%20build%20-%20Linux%20et%20al.md

under 2. Building dependencies -

The compiler want automake-1.16 but automake-1.17 is installed, at the end of the make I get the messages

 cd . && /bin/bash /home/rdu/Prusa/PrusaSlicer/deps/build/dep_MPFR-prefix/src/dep_MPFR/missing automake-1.16 --gnu
/home/rdu/Prusa/PrusaSlicer/deps/build/dep_MPFR-prefix/src/dep_MPFR/missing: Zeile 81: automake-1.16: Kommando nicht gefunden.
WARNING: 'automake-1.16' is missing on your system.


make[2]:  [CMakeFiles/dep_MPFR.dir/build.make:86: dep_MPFR-prefix/src/dep_MPFR-stamp/dep_MPFR-build] Fehler 2
make[1]:  [CMakeFiles/Makefile2:547: CMakeFiles/dep_MPFR.dir/all] Fehler 2
make: *** [Makefile:136: all] Fehler 2

 I get stuck

RE: Slicer 2.9.0 flatpak

I have automake-1.17 also. You can create a symlink with the name it expects, like "ln -s /usr/bin/automake-1.17 /usr/bin/automake-1.16".
Perhaps they have the version number hard-coded somewhere.

RE: Slicer 2.9.0 flatpak

Seems to be an issue found on git: #14081

RE: Slicer 2.9.0 flatpak

But the symlink workaround works for this.

RE: Slicer 2.9.0 flatpak

ok, the symlink is working too,  but I still get

configure: creating ./config.status
make[2]:  [CMakeFiles/dep_MPFR.dir/build.make:86: dep_MPFR-prefix/src/dep_MPFR-stamp/dep_MPFR-build] Fehler 2
make[1]:  [CMakeFiles/Makefile2:547: CMakeFiles/dep_MPFR.dir/all] Fehler 2
make: *** [Makefile:136: all] Fehler 2

RE: Slicer 2.9.0 flatpak

Now the forum hiccup has removed my how-to steps from yesterday evening how to get a successful build of PrusaSlicer. I'll wait some time before I'll try to post this again. Perhaps the forum will restore the posts somehow by itself.

RE:

Hi Walter, there are strange things going on the forum. I have received your posts on my mobile phone but when i tried to check on my PC I could not see your posts in the forum, even after login.

Also, when I logged in and clicked on the post entry I was logged out .... I had to click on logon again, ongoing .....

Anyway, Ill check out the script and try to figure out if the paths you are referring to are the same on my PC.

RE: Slicer 2.9.0 flatpak

I'm afraid that the script for replacing the definitions doesn't work.

In my environment I have  checked the path to link.txt - looks different.

./PrusaSlicer/deps/build/builds/Boost/libs/atomic/CMakeFiles/boost_atomic.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/timer/CMakeFiles/boost_timer.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/exception/CMakeFiles/boost_exception.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/serialization/CMakeFiles/boost_wserialization.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/serialization/CMakeFiles/boost_serialization.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/graph/CMakeFiles/boost_graph.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/random/CMakeFiles/boost_random.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/log/CMakeFiles/boost_log.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/log/CMakeFiles/boost_log_setup.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/type_erasure/CMakeFiles/boost_type_erasure.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/filesystem/CMakeFiles/boost_filesystem.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/url/CMakeFiles/boost_url.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/chrono/CMakeFiles/boost_chrono.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/program_options/CMakeFiles/boost_program_options.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/locale/CMakeFiles/boost_locale.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/container/CMakeFiles/boost_container.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/nowide/CMakeFiles/boost_nowide.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/thread/CMakeFiles/boost_thread.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/date_time/CMakeFiles/boost_date_time.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/coroutine/CMakeFiles/boost_coroutine.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/iostreams/CMakeFiles/boost_iostreams.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/context/CMakeFiles/boost_context.dir/link.txt
./PrusaSlicer/deps/build/builds/Boost/libs/json/CMakeFiles/boost_json.dir/link.txt
./PrusaSlicer/deps/build/builds/Blosc/blosc/CMakeFiles/blosc_static.dir/link.txt

all on standard Debian trixie installation

RE: Slicer 2.9.0 flatpak

This is the wrong step. The replacement is not needed for building the deps. Just start "make" and wait until the error message. Then cd into "....PrusaSlicer/deps/build/dep_MPFR-prefix/src/dep_MPFR" and type "autoreconf" there. This will fix the version mismatch for automake. After this go back into "....PrusaSlicer/deps/build/" and type "make" again. This will build the deps.
The replacement part is needed after the main build (2nd stage after the build of the deps) after the cmake there. I'm working on shortening it to a simple find one-liner. Will post that in a few minutes.