-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
README points to outdated build instructions #29
Comments
Welcome Vanessa to the Slic3r Prusa Edition. Would you please point me to the file I shoud modify? By the way, you are invited to enter your pressing needs into our issue tracker. |
The main README in your repo, i.e. this file: https://github.com/prusa3d/Slic3r/blob/master/README.md |
This should be taken care of the next time @bubnikv merges in from upstream, as it's correct there. The commit is slic3r/Slic3r@34f1853 |
Hi Vanessa, Sorry to butt in on your discussion (this is Win64 rather than Linux, but related to build instructions) but this seems like a good place to add my two cents. I have built the Win64 release version of prusa3d/Slic3r (twice now!) with these instructions. They could use some more work, but at least it was somewhat reproducible (for my setup). Windows 10.0.14393 Pro x64 Instructions for building slic3r for MSVC12 64-bitInstalling the dependencies:Installing MS Visual Studio 2013 (MSVC12.0) Expresshttps://www.microsoft.com/en-us/download/details.aspx?id=48134 Installing the Boost libraries:Slic3r is known to work with Boost 1.59.0. Boost 1.61.0 changed things and thus the build instructions do not work for it. or MSVC12 instructions: Note: This appears to build vc14, rather than vc12, but I'm not sure. In any case, it didn't work properly for me. In the end, it was much simpler to install the pre-built 64-bit Boost libraries from here (auto-download): Installing CygwinYou will need to have various Cygwin packages installed - start here: Archive: Base: Devel: Interpreters: Net: Shells: Text: Utils: Web: Add c:\cygwin64\bin to your PATH environment variable. Installing Perl (wperl64)Download the perl source from here: #About line 103 #About line 135 To configure a similar debug version, use: #About line 103 #About line 135 #About line 164 There are several other options available, including DebugSymbols (for a release version) and DebugFull – see the comments near line 148 in Makefile. FWIW, I only tried for a few minutes, but I was not able to successfully build wxWidgets (coming up shortly) using the debug configuration - complained about missing Module::Build. To build wperl64r, you need to open the VS2013 x64 Native Tools Command Prompt, which executes: "C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\vcvarsall.bat" amd64 in the command line. After the batch file finishes running, do the following: At this point, you are going to have to do some work to get the perl install finished (a number of packages are missing that are needed). Configure cpanWhen starting cpan from the command line for the first line, cpan will ask some questions and then create a user specific configuration file c:\Users\youruser.cpan\CPAN\MyConfig.pm FWIW again, I wasn't able to move the config file (and have it found by cpan) - does this need Windows registry enabled? Also, as I added new configurations, the original MyConfig.pm got clobbered. So, I created copies of the various configs (with better names, as I created them), and then copied the correct one to MyConfig.pm. You may also want/need to update cpan: Install cpanminus by running: It is convenient to create a startup script to set the environment for the perl & visual studio compiler suite to run. I made sure that wperl64 appears at the start of PATH, to ensure that it was used in preference to another version (such as cygwin). The initial contents of c:\wperl64r\cmdline_init.bat will be (there will be additions shortly): You will need to set the path to the Boost libraries in this file: It is also convenient to create a desktop shortcut to open a command line with the environment initialized: Installing wxWidgets 3.0.3 betaWe want to use the latest wxWidgets 3.0.3 beta, because it contains patches allowing us to enable multi sample anti aliasing in Slic3r 3D view. Get it here:https://github.com/discnl/wxWidgets/releases To disable optimization for more meaningful debugging, set the environment variable CL=/Od. By default, wxWidgets are compiled with the debugging information, without link time optimization. Rename (or copy) the lib\vc_x64_dll folder to lib\vc_dll after it has finished building. Set the WXDIR path (ideally in c:\wperl64d\cmdline_init.bat and restart the command line). Using the Installs directory example above, for example: Installing Alien-wxWidgets-0.67Download this particular version (0.67) from http://search.cpan.org/~mdootson/Alien-wxWidgets-0.67/lib/Alien/wxWidgets.pm and extract to the c:\Installs folder. Installing freeglut-2.8.1Get freeglut-2.8.1 here: Installing OpenGL-0.6704Note that any version other than 0.6704 causes the GUI to crash. Get OpenGL-0.6704 here: Extract the files, and apply two patches from OpenGL-0.6704-Win64.patch: patch glut_util.h OpenGL-0.6704-Win64.patch Copy all of the header files in c:\Installs\freeglut-2.8.1\include\GL to c:\Installs\OpenGL-0.6704\include\GL. set CL=/DFREEGLUT_STATIC /DNDEBUG /MD /DNO_STRICT nmake Installing Wx-0.9928Get Wx-0.9988 here: Then: set CL=-DNDEBUG You will need to edit the Makefile next. For ALL folder names, change the "/" to "" throughout the file - DON'T change the slashes in the URL names. There are also two sets of compiler flags that use slashes instead of dashes (search for /nologo) - change all of those flags to dashes. This is pretty ugly - you may want to save the Makefile - an "nmake clean" will blow away all your work. For some reason, I had to copy perllibst.h from c:\Installs\perl-5.24.0\win64 to C:\wperl64r\lib\CORE. Then: nmake This now fails somewhere that I can't find, but the fix is simple - copy the last command executed (it's pretty lengthy), paste it in the command window, and change "/" to "" in "script/make_ext_cccc", and hit return. Then, rerun the nmake command again (which should be successful). I'm sure somebody that understands nmake better than me (not difficult) can find the root cause of the problem. nmake test To run the wxdemo, install cpan install Wx::Demo and start wxperl_demo Installing Wx-GLCanvas-0.09Get Wx-GLCanvas-0.09 from here: Unpack Wx-GLCanvas-0.09.tar.gz. Apply two patches from Wx-GLCanvas-0.09-wx3.0.3-MSA.patch and four patches from Wx-GLCanvas-0.09-Win64.patch. patch GLCanvas.xs Wx-GLCanvas-0.09-wx3.0.3-MSA.patch patch GLCanvas.xs Wx-GLCanvas-0.09-Win64.patch perl Makefile.PL Install Math-LibmMath-Libm fails, because the Perl installation does not contain a working SSL module. Download it manually from here: Install slic3rDownload slic3r from alexrj or Prusa3D: This may fail in several places. My latest build using the Prusa3D master on 2016.11.21 built and ran flawlessly (many thanks to bubnikv and lordofhyphens)! Install IO-stringyIf this fails, you will need to install IO-stringy. Note the folder in which IO-stringy work was performed and failed (it will be in a folder named something like "wperl64r\cpanm\work\1234567890.12345" - it looks like a date/time stamp, so the folder names are always monotonically increasing). Then continue building slic3r (back in the slic3r folder): perl Build.PL Reinstalling OpenGL-0.6704The Build.PL in the previous step may have clobbered the version we installed, and it may need to be reinstalled. If so, go to C:\Installs\OpenGL-0.6704, and reinstall this version of OpenGL: cd C:\Installs\OpenGL-0.6704 Run slic3rAgain, back in the slic3r folder: perl slic3r.PL --gui |
Updated. Thanks. |
…ible (#29) Fix issue 9545 - make extra perimeters print first anchored then rest by sorting paths - breadth first search from anchored first
...at least for Linux. Build instructions for it are here, https://github.com/alexrj/Slic3r/wiki/Running-Slic3r-from-git-on-GNU-Linux
(see also the README for Slic3r upstream)
The text was updated successfully, but these errors were encountered: