Building Slic3r PE on Microsoft Windows

The currently supported way of building Slic3r PE on Windows is with CMake and MS Visual Studio 2013. You can use the free Visual Studio 2013 Community Edition. CMake installer can be downloaded from the official website.

Building with newer versions of MSVS (2015, 2017) may work too as reported by some of our users.

Note: Thanks to @supermerill for testing and inspiration for this guide.

Dependencies

On Windows Slic3r is built against statically built libraries. We provide a prebuilt package of all the needed dependencies. This package only works on Visual Studio 2013, so if you are using a newer version of Visual Studio, you need to compile the dependencies yourself as per below. The package comes in a several variants:

64 bit, Release mode only (41 MB, 578 MB unpacked)
64 bit, Release and Debug mode (88 MB, 1.3 GB unpacked)
32 bit, Release mode only (38 MB, 520 MB unpacked)
32 bit, Release and Debug mode (74 MB, 1.1 GB unpacked)

When unsure, use the Release mode only variant, the Release and Debug variant is only needed for debugging & development.

If you're unsure where to unpack the package, unpack it into C:\local\ (but it can really be anywhere).

Alternatively you can also compile the dependencies yourself, see below.

Building Slic3r PE with Visual Studio

First obtain the Slic3r PE sources via either git or by extracting the source archive.

Then you will need to note down the so-called 'prefix path' to the dependencies, this is the location of the dependencies packages + \usr\local appended. For example on 64 bits this would be C:\local\destdir-64\usr\local. The prefix path will need to be passed to CMake.

When ready, open the relevant Visual Studio command line and cd into the directory with Slic3r sources. Use these commands to prepare Visual Studio solution file:

mkdir build
cd build
cmake .. -G "Visual Studio 12 Win64" -DCMAKE_PREFIX_PATH="<insert prefix path here>"

Note that if you're building a 32-bit variant, you will need to change the "Visual Studio 12 Win64" to just "Visual Studio 12".

Conversely, if you're using Visual Studio version other than 2013, the version number will need to be changed accordingly.

If cmake has finished without errors, go to the build directory and open the Slic3r.sln solution file in Visual Studio. Before building, make sure you're building the right project (use one of those starting with slic3r_app_...) and that you're building with the right configuration, i.e. Release vs. Debug. When unsure, choose Release. Note that you won't be able to build a Debug variant against a Release-only dependencies package.

Installing using the `INSTALL` project

Slic3r PE can be run from the Visual Studio or from Visual Studio's build directory (src\Release or src\Debug), but for longer-term usage you might want to install somewhere using the INSTALL project. By default, this installs into C:\Program Files\Slic3r. To customize the install path, use the -DCMAKE_INSTALL_PREFIX=<path of your choice> when invoking cmake.

Building from the command line

There are several options for building from the command line:

To build with msbuild, use the same CMake command as in previous paragraph and then build using

msbuild /m /P:Configuration=Release ALL_BUILD.vcxproj

To build with Ninja or nmake, replace the -G option in the CMake call with -G Ninja or -G "NMake Makefiles" , respectively. Then use either ninja or nmake to start the build.

To install, use msbuild /P:Configuration=Release INSTALL.vcxproj , ninja install , or nmake install .

Building the dependencies package yourself

The dependencies package is built using CMake scripts inside the deps subdirectory of Slic3r PE sources. (This is intentionally not interconnected with the CMake scripts in the rest of the sources.)

Open the preferred Visual Studio command line (64 or 32 bit variant) and cd into the directory with Slic3r sources. Then cd into the deps directory and use these commands to build:

mkdir build
cd build
cmake .. -G "Visual Studio 12 Win64" -DDESTDIR="C:\local\destdir-custom"
msbuild /m ALL_BUILD.vcxproj

You can also use the Visual Studio GUI or other generators as mentioned above.

The DESTDIR option is the location where the bundle will be installed. This may be customized. If you leave it empty, the DESTDIR will be placed inside the same build directory.

Warning: If the build directory is nested too deep inside other folders, various file paths during the build become too long and the build might fail due to file writing errors (*). For this reason, it is recommended to place the build directory relatively close to the drive root.

Note that the build variant that you may choose using Visual Studio (i.e. Release or Debug etc.) when building the dependency package is not relevant. The dependency build will by default build both the Release and Debug variants regardless of what you choose in Visual Studio. You can disable building of the debug variant by passing the

-DDEP_DEBUG=OFF

option to CMake, this will only produce a Release build.

Refer to the CMake scripts inside the deps directory to see which dependencies are built in what versions and how this is done.

*) Specifically, the problem arises when building boost. Boost build tool appends all build options into paths of intermediate files, which are not handled correctly by either b2.exe or possibly ninja (?).

6.2 KiB Raw Blame History