- Download Slic3r Perl.
- Install it, following the on screen instruction. Basically that means keep clicking Next.
Slic3r is known to work with Boost 1.63.0. Note: Dev version prior to 27/03/2017 worked ok with boost 1_59_0. If you have that installed, you need to erase the folder c:\dev\boost_1.59_0\ and then install and compile the new boost libraries, following the next instructions
Download them from the Boost website. The official binaries won't work since they're compiled for MSVC. Extract the sources to C:\dev\boost_1_63_0. Run the following instructions from the Perl command prompt
cd C:\dev\boost_1_63_0
bootstrap.bat gcc
b2 toolset=gcc cxxflags="-std=c++11" link=static runtime-link=static variant=release threading=multi
For our custom Perl package of 5.24, use the prebuilt dependency archive. It includes wxWidgets 3.1.0, because wxWidgets 3.0.2 does not build with newer GCC versions. See [[Building wxWidgets 3.1.0]] for more information about custom-building wxWidgets if you really want to build it yourself.
Open a command prompt and move to the directory where you want to create a Slic3r working copy.
Then issue this command: git clone git://github.com/alexrj/Slic3r.git or git clone http://github.com/alexrj/Slic3r.git
It will create a Slic3r directory in the current position. Issue git checkout windows-build32 to switch to the stable branch (fewer changes).
Note: the custom perol package seems to not have cpanm. at then moment of executeing the git clone git://github.com/alexrj/Slic3r.git you will get a message about that, follow the instructions to install cpanminus and continue again
- After getting the sources, you will have a slic3r folder created, inside this floder extract the content of prebuilt dependency archive, and then continue with next step. Dont try to build the GUI without this dependencies, it wont work
- First, verify your Perl command environment is working. Start the prompt as stated above, then type
perl -v. You should get some meaningful message. Check your perl installation if not. - Now cd to the folder where Slic3r source code is cloned, and proceed with the build process to verify the dependence installed:
cd Slic3r
perl Build.PL
perl Build.PL --gui
If you got the dependencies installed, now you could fire up the Slic3r with still in the command prompt by:
perl slic3r.pl
If you want to have a simple exe file to run Slic3r from (instead of invoking perl), open a Powershell window and cd to package/win and run & .\compile_wrapper.ps1 524. This will put 3 exe files in the same directory; either copy these files to the root Slic3r directory and/or run & .\package_win32.ps1 to make a zip file (similar to how our build server works). The former approach is fine if you aren't going to distribute Slic3r to machines that don't have slic3r-perl installed.