![]() When building on ubuntu 20.04 focal fossa, the package libwxgtk3.0-gtk3-dev needs to be installed instead of libwxgtk3.From the command line, cmake can be run as an interactive question and answer session or as a non-interactive program. ![]() Note that while PrusaSlicer can be linked against wWidgets 3.0, the combination is not well tested and there might be bugs in the resulting application. ![]() If you want to link against wxWidgets 3.0 (which are still provided by most distributions because wxWidgets 3.1 have not yet been declared stable), you must set -DSLIC3R_WX_STABLE=ON when running CMake. Our build script in fact downloads specific patched version of wxWidgets. wxWidgetsīy default, PrusaSlicer looks for wxWidgets 3.1. It is possible to look at your distribution PrusaSlicer package to see how the package maintainers solved the dependency issues. If you decide to build this way, it is your responsibility to make sure that CMake finds all required dependencies. Some of the dependencies don't have to be as recent as the versions listed - generally versions available on conservative Linux distros such as Debian stable, Ubuntu LTS releases or Fedora are likely sufficient. The list of dependencies can be easily obtained by inspecting the CMake scripts in the deps/ directory. Feel free to do so, but you are on your own. Building dynamicallyĪs already mentioned above, dynamic linking of dependencies is possible, but PrusaSlicer team is unable to troubleshoot (Linux world is way too complex). See the CMake files to get the complete list. -DSLIC3R_GUI=no to build the console variant of PrusaSlicer.-DCMAKE_BUILD_TYPE=Debug to build in debug mode (defaults to Release).-DSLIC3R_WX_STABLE=ON to look for wxWidgets 3.0 (defaults to OFF).-DSLIC3R_STATIC=ON for static build (defaults to OFF).Note that wxWidgets must be built against the same GTK version. -DSLIC3R_GTK=3 to use GTK3 (defaults to 2).-DSLIC3R_ASAN=ON enables gcc/clang address sanitizer (defaults to OFF, requires gcc>4.8 or clang>3.1).Useful CMake flags when building PrusaSlicer DDEP_WX_GTK3=ON builds wxWidgets (one of the dependencies) against GTK3 (defaults to OFF) Can be useful for repeated builds, to avoid unnecessary network traffic. DDEP_DOWNLOAD_DIR= specifies a directory to cache the downloaded source packages for each library. When not provided, the script creates and uses destdir directory where cmake is run. DDESTDIR= allows to specify a directory where the dependencies will be installed. Useful CMake flags when building dependencies ![]() Unless that's already the case, install them as usual from your distribution packages. GNU build tools, CMake, git and other libraries have to be installed on the build machine. ![]() Linking on a 4GB RAM system will likely fail and you may need to limit the number of compiler processes with the '-j xxx' make or ninja parameter, where 'xxx' is the number of compiler processes launched if running on low RAM multi core system, for example on Raspberry PI. You need at least 8GB of RAM on your system. Running all the listed commands in order should result in successful build. This guide describes building PrusaSlicer statically against dependencies pulled by our deps script. Instead of compiling PrusaSlicer from source code, one may also consider to install PrusaSlicer pre-compiled by contributors. If you have some reason to link dynamically to your system libraries, you are free to do so, but we can not and will not troubleshoot any issues you possibly run into. We can only support PrusaSlicer statically linked against the dependencies compiled with the deps scripts, the same way we compile PrusaSlicer for our binary builds. Namely, we cannot help troubleshoot OpenGL driver issues or dependency issues if compiled against distro provided libraries. Please understand that PrusaSlicer team cannot support compilation on all possible Linux distros. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |