Disable Printables tab in Prusaslicer?
 
Notifications
Clear all

Disable Printables tab in Prusaslicer?  

Page 2 / 2
  RSS
Jára
(@jara)
Estimable Member
RE: Disable Printables tab in Prusaslicer?

Sorry, I am lost.

I have followed this manual: https://github.com/prusa3d/PrusaSlicer/blob/master/doc/How%20to%20build%20-%20Windows.md

 Detecting CXX compile features - done
CMake Error at CMakeLists.txt:5 (find_package):
By not providing "FindQhull.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Qhull", but
CMake did not find one.

Could not find a package configuration file provided by "Qhull" (requested
version 7.2) with any of the following names:

QhullConfig.cmake
qhull-config.cmake

Add the installation prefix of "Qhull" to CMAKE_PREFIX_PATH or set
"Qhull_DIR" to a directory containing one of the above files. If "Qhull"
provides a separate development package or SDK, be sure it has been
installed.

Configuring incomplete, errors occurred!
See also "O:/temp/PRUSA/PrusaSlicer/src/build/CMakeFiles/CMakeOutput.log".

Posted : 13/02/2026 9:36 pm
Walter Layher
(@walter-layher)
Noble Member
RE:

That is the same guide that I followed, and specifically the one under "2.A Manual Build Instructions"

What version of Visual Studio do you have installed?

I installed all the apps I mentioned in my post only today. It is a recent install of Windows 11 from November or thereabout with only Office installed and not much else.

Also perhaps important for this: do not use the standard windows cmd shell for the build, but the special command shell that came with Visual Studio. It has some elements in the path that the standard cmd has not.

Posted : 13/02/2026 9:42 pm
Jára
(@jara)
Estimable Member
RE:

Automatic build also fails, see the file attached.

I have installed MSVC 2019, 2013 and 2010. CMAKE 3.18.

 
CMD shell from MSVC did not help, it also fails.
This post was modified 50 mins ago by Jára
Posted : 13/02/2026 9:47 pm
Walter Layher
(@walter-layher)
Noble Member
RE:

I had MSVC 2026 installed first, then I also installed MSVC 2022 (keeping MSVC 2026 installed) and when I started the build, it found and used some stuff from MSVC 2026 and failed. So I deinstalled both versions of MSVC, rebooted and then only installed MSVC 2022. After that it worked.

Your attachment does not work, maybe you should zip the file first.

Posted : 13/02/2026 9:52 pm
Page 2 / 2
Share: