Search Criteria
Package Details: android-armv7a-eabi-qt6-shadertools 6.9.2-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/android-armv7a-eabi-qt6-shadertools.git (read-only, click to copy) |
---|---|
Package Base: | android-armv7a-eabi-qt6-shadertools |
Description: | Experimental module providing APIs and a host tool to host tool to perform graphics and compute shader conditioning for the upcoming Qt graphics abstraction layer (android) |
Upstream URL: | https://www.qt.io |
Licenses: | custom, GPL3, LGPL3, FDL |
Groups: | android-armv7a-eabi-qt6 |
Submitter: | Martchus |
Maintainer: | Martchus |
Last Packager: | Martchus |
Votes: | 0 |
Popularity: | 0.000000 |
First Submitted: | 2024-10-15 01:41 (UTC) |
Last Updated: | 2025-08-30 23:44 (UTC) |
Dependencies (5)
- android-armv7a-eabi-qt6-baseAUR
- android-cmakeAUR (make)
- ninja (ninja-kitwareAUR, ninja-fuchsia-gitAUR, ninja-gitAUR, ninja-memAUR, ninja-noemacs-gitAUR, ninja-jobserverAUR) (make)
- qt6-shadertools (make)
- qt6-shadertools (optional) – development tools
Latest Comments
hantz commented on 2025-09-15 23:46 (UTC)
Yeah that's fair. The issue is with my AUR helper. I'll figure that out. Thanks for maintaining all these packages BTW!
Martchus commented on 2025-09-15 08:07 (UTC)
When building packages from the AUR you have to make sure yourself to build them in the correct order. So you have to build e.g.
android-armv7a-eabi-qt6-base
first and only thenandroid-armv7a-eabi-qt6-shadertools
. Not sure what you mean with "but I prefer to upgrade everything all at once". That's not really how building packages from the AUR works. You'll have to invoke makepkg (or preferably makechrootpkg) for each PKGBUILD in the right order or use an AUR helper that does this in the right order.Note that
-DQT_NO_PACKAGE_VERSION_CHECK=TRUE
is only appropriate for dealing with the case when e.g.qt6-shadertools
andandroid-armv7a-eabi-qt6-shadertools
have different versions. This should normally not be the case for too long, though. I would refrain from adding this by default because the build might nevertheless break due to an incompatibility and I don't want to have to debug these cases.hantz commented on 2025-09-15 02:30 (UTC)
This package is updated at the same time as
android-armv7a-eabi-qt6-base
. So it's built before the base package has been installed. Causing the build to fail with this error:This also happens with other related packages like
android-armv7a-eabi-qt6-serialport
. Should the suggested flag (-DQT_NO_PACKAGE_VERSION_CHECK=TRUE
) be added tobuild
in the PKGBUILD? Doing that made the error go away, but I haven't tested enough yet to tell if that is appropriate.AFAIK there should not be any breaking changes between minor (let alone patch) versions of Qt, couldn't the required version be less strict, e.g. 6.9 or 6 instead of 6.9.2? A
_qtver
variable is defined in the PKGBUILD with the full version. Of course one can always install the base package first and then upgrade this, but I prefer to upgrade everything all at once.