Compiling PrusaSlicer
Hello,
I want to share with the community my improvements to PrusaSlicer.
The first approach was just to download the PrusaSlicer 2.0.0 sources from the ZIP file in the main PRUSA GitHub page ( https://github.com/prusa3d/PrusaSlicer/archive/version_2.0.0.zip).
I was able to compile it with Visual Studio Community 2013 and make the new MMU2 implementation.
However this is not useful to the community, so I decided to redo the work in an official GitHub way.
- I made a fork of the PrusaSlicer repository.
- Then I GIT cloned the repository in my PC.
- But when I tried to compile it, I discovered that it can not be compiled. It raised an error :
...prusaslicer\src\libslic3r\pchheader.hpp(105): fatal error C1083: Cannot open include file: 'cereal/access.hpp'
: No such file or directory [PrusaSlicer\build\src\libslic3r\libslic3r.vcxproj]It seems that several slic3r header files have been missed from the github repo.
- Even searching on internet and adding the missing library files, do not allow to the sources to be compiled, because the the compiler raised other errors related to unsupported source code syntax.
- Is it clear that the repository is a working in progress with no apparently stable branch.
In theory I would have expected to have the Master branch corresponding at the latest stable PrusaSlicer 2.0.0, but it was not.
I compared the GitHub source code that does not compile, with the source code contained into the downloaded ZIP, that can be compiled with no issues, and the code is very very different...
In facts the ZIP is between the preloaded archived source code, and NOT a ZIP of the current repository code.
My question is: what is the PRUSA GitHub branch name corresponding to the "stable" distributed PrusaSlicer 2.0.0 (in the ZIP) .
It is clear that is not the Master (!!!). There are a lot of develop branches, but no clear indication of what is the stable version that can be compiled, if exists.
- Can someone between the PRUSA developers help us and give some indications on how to proceed ?
Regards
RE: Compiling PrusaSlicer
Welcome to open source ... and why there are so many bugs that reappear as versions get released. Regression testing? What's that?
Sorry - but it's no longer fun to find once dependable features disappear when a new release is posted.
ps: Your post is best made on the GitHub pages - the "devs" rarely read forum posts. And if you want real feedback, try finding bubuvik (sic). He doesn't take criticism of his code very well, but he is most likely to at least listen.
RE: Compiling PrusaSlicer
master branch version_2.0.0 tag
RE: Compiling PrusaSlicer
try finding bubuvik (sic). He doesn't take criticism of his code very well, but he is most likely to at least listen.
It's Vojtech Bubnik (user: bubnikv)
And he takes criticism very well as long as it's delivered in an appropriate manner.
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
RE: Compiling PrusaSlicer
It's Vojtech Bubnik (user: bubnikv)
And he takes criticism very well as long as it's delivered in an appropriate manner.
Peter
The few times I've brought up code issues, he seemed pretty sensitive. Though, my delivery can be a bit harsh.
Thanks for the correct name.
RE: Compiling PrusaSlicer
Many thanks David.
I was able to find the Release 2.0.0 using the tag. I am still getting familiarity with GitHub.
I added the changes to add the new features, and recompiled all successfully.
Now I need only to update GitHub and the PrusaSlicer 2.0.0 CE with MMU2 Tool change temperature support will be available to the open-source community.
Regards
RE: Compiling PrusaSlicer
I dont know how still this problem is occurring. Me too before reaching to this thread got dumped to into page of another language