3 Commits

Author	SHA256	Message	Date
Benjamin Greiner	bbaa80a2eb	Accepting request 828264 from home:bnavigator:branches:science ... - revert the memoryperjob change. The build process really acquires that much memory per job and the workers cannot provide 3GB per CPU core. Sadly, we are limited by memory not by CPU cores. - require 11 GB of RAM. This allows us to run 3 jobs in parallel and can be provided by all architectures OBS-URL: https://build.opensuse.org/request/show/828264 OBS-URL: https://build.opensuse.org/package/show/science/PrusaSlicer?expand=0&rev=13	2020-08-20 19:00:03 +00:00
Benjamin Greiner	3318c426da	Accepting request 828118 from home:marxin:memory-constraint ... - Use memoryperjob constraint instead of %limit_build macro. - Use only 1GB for memoryperjob. Memory and CPU usage graph can be seen here: 79a999743a/PrusaSlicer.svg OBS-URL: https://build.opensuse.org/request/show/828118 OBS-URL: https://build.opensuse.org/package/show/science/PrusaSlicer?expand=0&rev=12	2020-08-20 10:48:47 +00:00
Dirk Stoecker	4e4cd055fa	Accepting request 787172 from home:bnavigator:branches:science ... - update to version 2.2.0 introducing SLA hollowing and hole drilling, support for 3rd party printer vendors, 3Dconnexion support, automatic variable layer height, macOS dark mode support, greatly improved ColorPrint feature and much, much more. See https://github.com/prusa3d/PrusaSlicer/releases/tag/version_2.2.0 and the changelogs for the release candidates, betas and alphas since 2.1.1 for a complete list of changes. - reactivate parallel builds, but need strong enough workers and reserve 4G of memory per thread (memory-constraints, %limit_build) - new build dependencies: cgal, ilmbase, more of boost, libudev, openvdb OBS-URL: https://build.opensuse.org/request/show/787172 OBS-URL: https://build.opensuse.org/package/show/science/PrusaSlicer?expand=0&rev=4	2020-03-25 16:54:58 +00:00