Package Details: orca-slicer 1:2.3.2-6

Git Clone URL: https://aur.archlinux.org/orca-slicer.git (read-only, click to copy)
Package Base: orca-slicer
Description: G-code generator for 3D printers (Bambu, Prusa, Voron, VzBot, RatRig, Creality, etc.)
Upstream URL: https://github.com/SoftFever/OrcaSlicer
Keywords: bambustudio orca orcaslicer slicer
Licenses: AGPL-3.0-only
Conflicts: orca-slicer
Provides: orca-slicer
Submitter: xburst
Maintainer: c2h5oh (lod)
Last Packager: c2h5oh
Votes: 39
Popularity: 3.37
First Submitted: 2023-03-29 15:51 (UTC)
Last Updated: 2026-04-17 23:17 (UTC)

Latest Comments

1 2 3 4 5 6 .. 17 Next › Last »

zebulon commented on 2026-05-20 14:03 (UTC)

FYI the Software Freedom Conservancy has set up a new repository for OrcaSlicer with Paweł Jarczak's patches to allow communicating with Bambu Studio's server side components that did not require replacing or modifying the dynamically linked libraries. Repo is there: https://f.sfconservancy.org/baltobu/orca-slicer-for-bambu and the analysis is there: https://sfconservancy.org/news/2026/may/18/bambu-studio-3d-printer-agpl-violation-response/

Any interest in packaging it?

c2h5oh commented on 2026-04-17 23:26 (UTC)

@projectgus done, but quick test of both versions yields roughly the same CPU load and memory use for both versions. Not very scientific testing mind you, just checking htop every now and then during the build.

projectgus commented on 2026-04-17 22:31 (UTC) (edited on 2026-04-17 23:38 (UTC) by projectgus)

@c2h5oh Sorry to be a pain, but I think you have to apply one more change before CMAKE_BUILD_PARALLEL_LEVEL will work for the main orca-slicer build:

diff --git i/PKGBUILD w/PKGBUILD
index 4c8681b..3a05794 100644
--- i/PKGBUILD
+++ w/PKGBUILD
@@ -64,7 +64,7 @@ build() {
     -DBBL_INTERNAL_TESTING=0 \
     -DCMAKE_BUILD_TYPE=Release \
     -DCOLORED_OUTPUT=ON
-  ninja -C build
+  cmake --build build

   # add localizations
   ./scripts//run_gettext.sh --full

(Recommend also changing the same line for the deps build, for consistency. But this one is necessary as CMAKE_BUILD_PARALLEL_LEVEL causes CMake to generate a -j value for ninja internally - ninja doesn't know about this environment variable otherwise.)

c2h5oh commented on 2026-04-17 20:12 (UTC)

New version includes following changes:

  • backports patch by @projectgus to v2.3.2 to fix Orca issue that caused memory and cpu usage to go crazy during deps build
  • increases build parallelism to number of threads or available memory in GB, whichever is lower (used to be one for every 2 GB, but it turns out that's too conservative)
  • updated Github source download url - the old one started giving intermittent 404 errors suggesting it's a brownout to get us to use the new ones

Yes, recent changes caused the build to take about 30% longer, but it should now build on systems with 16GB and possibly even 8GB RAM (report back if it doesn't!) and it doesn't slow your PC to a crawl like it used to during some stages of the build.

Samueru commented on 2026-04-14 16:02 (UTC)

Fails to build: https://pastebin.com/RPwKpGqX

projectgus commented on 2026-04-09 06:27 (UTC) (edited on 2026-04-09 06:30 (UTC) by projectgus)

@c2h5oh Appreciate you looking into the parallel build issue! CMAKE_BUILD_PARALLEL_LEVEL only works when the build stage is run via cmake --build, so some extra PKGBUILD changes are needed before this limit takes effect. Patch that worked for me: https://gist.github.com/projectgus/da22740e449e4428c0193e2bcafa75ba#file-orca-slicer-aur-patch

I found free_memory_in_GB/2 left quite a bit of free memory & idle CPU during the build, I did some experimenting and seems I can build with free_memory_in_GB jobs and see no memory pressure (with nprocs=24, RAM=32GB total and 19GB free). Without any limit at all the build would always trigger oomkiller. A safe divider might be 1.2 or 1.5?

The orcaslicer dependency build still overrides the CMAKE_BUILD_PARALLEL_LEVEL setting at the moment and always runs each child dependency build with -j$(nprocs). I've submitted a patch for this upstream: https://github.com/OrcaSlicer/OrcaSlicer/pull/13158

c2h5oh commented on 2026-04-07 16:47 (UTC)

@rlavriv thanks to a painfully boring all-hands meeting this is now fixed

c2h5oh commented on 2026-04-07 16:05 (UTC)

@rlavriv it looks like there is an extra space after the number. I'll fix it after work.

rlavriv commented on 2026-04-07 15:56 (UTC)

I am getting build error with the latest orca-slicer:

[22/193] Performing build step for 'dep_GLEW' FAILED: [code=1] dep_GLEW-prefix/src/dep_GLEW-stamp/dep_GLEW-build /home/rlavriv/.cache/yay/orca-slicer/src/OrcaSlicer-2.3.2/deps/build/dep_GLEW-prefix/src/dep_GLEW-stamp/dep_GLEW-build cd /home/rlavriv/.cache/yay/orca-slicer/src/OrcaSlicer-2.3.2/deps/build/dep_GLEW-prefix/src/dep_GLEW-build && /usr/bin/cmake --build . --config Release -- -j12 && /usr/bin/cmake -E touch /home/rlavriv/.cache/yay/orca-slicer/src/OrcaSlicer-2.3.2/deps/build/dep_GLEW-prefix/src/dep_GLEW-stamp/dep_GLEW-build 'CMAKE_BUILD_PARALLEL_LEVEL' environment variable invalid number '7 ' given.

Devnol commented on 2026-04-07 11:36 (UTC)

Good to hear, however I've since switched to orca-slicer-bin which ships pre-compiled AppImage which appears to have the issues I had before with it resolved (I don't even remember what it was but last I tried it I had some problems with it). May be a good alternative for anyone lacking the power to compile themselves.

1 2 3 4 5 6 .. 17 Next › Last »