@taotieren

That's unfortunate serial-studio-bin uses Appimage, which I was trying to avoid.

For now I've taken the plunge and upgraded to Qt 6.10 after compiling against 6.9.2. Qt is not guaranteed to be ABI compatible, so it might break at some point. But as long as I don't use the multi-plot I should be good until a fix is released.

Also I noticed that this package does not install a .desktop entry (unlike serial-studio-bin)?

Build is currently broken, arch automatically updates qt6 to version 6.10.0.

However the latest release does not build against 6.10.0 due to a build flag enabling a non-existing function when building against > 6.10.0

See https://github.com/Serial-Studio/Serial-Studio/issues/321

This is already fixed in a later commit, but not released yet.

Could this package be downgraded to version 3.1.7, which seems to be the last version that is able to build against QT 6.10.0. For know i've downgraded qt to 6.9.2, however this make me unable to update my system, unfortunately.

@taotieren Thanks for your change - I just tested it - it works great

PS: I just had a look at your build - and just want to clarify a little detail. Even with my suggested change you can still have ninja as the selected "builder" (-G Ninja). As long as you invoke the builder through cmake it can be resource limited as I suggested. But there can be lots of other reasons for the removal of '-G Ninja' - I just wanted to give you some feedback on the change :-)

@uffe Thanks, I've committed the changes to cmake, if local compilation is slow, you can add my repositories to download the pre-compiled packages.

Could you please do a little change to your PKGBUILD ?

Specificly change ninja -C build into cmake --build build

Reasoning:

With ninja it is unfortunately not possible to control its number of parallel builders with environment variables.

That is a feature that both make and cmake have.

The ninja folks refuse to make such feature.

When I aur-build serial-studio on my old laptop - ninja will spawn so many parallel builders that it runs out of memory during compile pass...

Normally you can do resource control of aur builds via makepkg.conf - that does unfortunately not work when invoking ninja directly - so every time I have to edit PKGBUILD - to prevent from running out of memory.

with the above suggested change the end result is the same - instead of invoking ninja directly - you just use cmake to invoke the (ninja) builder - but with cmake as the invoking frontend you (I) can just put limitations into my local makepkg.conf:

CMAKE_BUILD_PARALLEL_LEVEL=2 MAKEFLAGS="-j2"

The above will work for any aur build that use make and cmake (but not if you invoke ninja directly)

Thanks in advance :-)