@gerliczkowalczuk if you interested, I also work on a build against system deps. Right now I got everything working except OpenSSL, CURl and wxWidgets. Upstream switched to the wxWidgets dev branch. wxWidgets should fix itself, when they move to the 3.4 stable later this year. I haven't really checked why Orca still depends on OpenSSL 1.1.1 yet.

I'll clean up the build today or tomorrow and if you want to, I will send you a mail for tests, feedback and help.

@lod Thanks for working on the update. If you need any help with testing or packaging, feel free to let me know.

@gerliczkowalczuk I'm on it, I just waited if c2h5oh wants to do anything. No harm in waiting a couple of days ;)

@c2h5oh, if you no longer have time to maintain this package (which I completely understand), I would be happy to be added as a co-maintainer so that I can help keep the package up to date.

@c2h5oh are you already cooking a 2.4 build?

The current script limits the number of threads (CMAKE_BUILD_PARALLEL_LEVEL) to free memory in gigabytes. With a longer running machine (at least my machine) this evaluates to 0 even though there were 12 GB of available memory, which causes the build to fail (as, somewhere down the line, some dependency complained that CMAKE_BUILD_PARALLEL_LEVEL must be a positive integer). I would suggest switching to looking at MemAvailable instead of MemFree. See also https://www.linuxatemyram.com/.

So I've attempted to build this 3x on my machine, and it ends up killing the build, as well as pretty much every other non-critical process on my machine, due to "Out of memory."

The machine specs are:

Ryzen 5800h 16GB system RAM RTX3070 8GB GPU

I have two modifications in my makepkg.conf from stock/baseline: MAKEFLAGS="-j2" => "-j4" CFLAGS="-march=x86-64 -mtune=generic ..." => "-march=native ..."

I tried turning them off, and it still happens. In addition, it bogs the machine way down within about 5 seconds of starting the build.

@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.

@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.)