Package Details: qgroundcontrol 4.4.4-2

Git Clone URL: https://aur.archlinux.org/qgroundcontrol.git (read-only, click to copy)
Package Base: qgroundcontrol
Description: Micro air vehicle ground control station.
Upstream URL: https://github.com/mavlink/qgroundcontrol
Licenses: GPL3
Submitter: anselmolsm
Maintainer: edombek
Last Packager: edombek
Votes: 13
Popularity: 0.012539
First Submitted: 2016-05-13 13:37 (UTC)
Last Updated: 2025-03-29 12:33 (UTC)

Latest Comments

1 2 3 4 5 6 Next › Last »

edombek commented on 2025-10-23 13:52 (UTC)

@berilac OK. Thanks.

berilac commented on 2025-10-23 13:21 (UTC) (edited on 2025-10-23 13:32 (UTC) by berilac)

@edombek I managed to get a working build, but so far only with the master branch (which is apparently using v5.0.3).

Wanted to use the Stable_V5.0 branch (currently at v5.0.8) but that won't compile yet with Qt 6.10.0. It expects 6.8.3.

In keeping somewhat with the oldskool, I will continue to try and get a working source build of QGC v5.0.8 using Qt 6.10.0.

If I manage it I'll let you know, in case you're interested in a non-appimage approach.

edombek commented on 2025-10-23 12:45 (UTC)

@berilac I'm not quite sure yet how to neatly resolve the version conflict to build a fresh version. I think I should use appimage.

berilac commented on 2025-10-23 06:13 (UTC) (edited on 2025-10-23 06:39 (UTC) by berilac)

@edombek are you having any luck reworking the PKGBUILD for new versions (qt6, no more qmake, etc)? I'm trying myself at the moment, though it's looking like it may end up being a qgroundcontrol-git package instead.

The build instructions for qgroundcontrol seem to explicitly state we should specifically use qt v6.10.0. My current approach is just trying to make use of arch's qt6 packages. However, I'm also looking into using the "offline sources".

I've linked to the split source modules because if we don't need qtwebengine we can avoid an 840M to 1.3G download; it's clearly the worst culprit for size, an order or two magnitude larger than the other modules. I'm just not sure how to best determine which modules we actually need without trial and error.

berilac commented on 2025-09-05 10:01 (UTC)

Looks like libsystemd should be an optdepends. I successfully compiled on artix after commenting it out.

edombek commented on 2025-08-26 12:46 (UTC)

I prepared a PKGBUILD for the new version, but for now we have an error: https://github.com/mavlink/qgroundcontrol/issues/13049

edombek commented on 2025-03-29 12:34 (UTC)

Hi! Thanks for the comment. Fixed.

jacko commented on 2025-03-29 11:53 (UTC) (edited on 2025-03-29 11:54 (UTC) by jacko)

Hi there, thanks for taking on maintenance edombek!

Would it be possible to change the qmake line to the following:

qmake CONFIG+=StableBuild ..

Then the window title will show up as "QGroundControl" instead of "QGroundControl Daily". Also I believe QGC allows for the app settings to be stored in different directories for the daily and release versions. This change would allow for better compatibility with a parallel install of Qgroundcontrol Daily, which I find I need when messing around with drones.

igoutta commented on 2025-02-24 07:00 (UTC)

In the Desktop Entry, I strongly recommend adding "-platform xcb" at the end of the Exec tag to ensure proper compatibility with the Wayland compositor.

1 2 3 4 5 6 Next › Last »