I have tried both the gtk2 version and the qt5 version and contrary to
what you claim, the gtk2 version is completely broken with black
artifacts flickering on the screen while the qt5 version is playable.

This is with XFCE (X11) on an arm64 machine. The debdiff of my qt5
experiment is attached (not a patch for the actual package) to
demonstrate how I have built it.
diff -Nru c-evo-dh-3.1/debian/changelog c-evo-dh-3.1/debian/changelog
--- c-evo-dh-3.1/debian/changelog       2025-11-28 17:11:02.000000000 +0000
+++ c-evo-dh-3.1/debian/changelog       2026-02-11 19:45:15.000000000 +0000
@@ -1,3 +1,10 @@
+c-evo-dh (3.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install the qt5 version as "-gtk2" binary.
+
+ -- Bastian Germann <[email protected]>  Wed, 11 Feb 2026 19:45:15 +0000
+
 c-evo-dh (3.1-1) unstable; urgency=medium
 
   * New upstream version (Add Indians Tribe)
diff -Nru c-evo-dh-3.1/debian/control c-evo-dh-3.1/debian/control
--- c-evo-dh-3.1/debian/control 2025-11-17 18:42:48.000000000 +0000
+++ c-evo-dh-3.1/debian/control 2026-02-11 15:41:49.000000000 +0000
@@ -5,7 +5,7 @@
 Section: games
 Priority: optional
 Build-Depends: debhelper-compat (= 13)
-Build-Depends-Arch: fpc, lcl, lcl-gtk2, libjpeg-dev, libgtk2.0-dev
+Build-Depends-Arch: fpc, lcl, lcl-qt5, libjpeg-dev
 Standards-Version: 4.7.2
 Homepage: https://sourceforge.net/projects/c-evo-eh/
 Vcs-Browser: https://salsa.debian.org/debian/c-evo-dh
diff -Nru c-evo-dh-3.1/debian/rules c-evo-dh-3.1/debian/rules
--- c-evo-dh-3.1/debian/rules   2025-08-10 20:13:30.000000000 +0000
+++ c-evo-dh-3.1/debian/rules   2026-02-11 19:43:36.000000000 +0000
@@ -18,6 +18,9 @@
 export LibDir   = /lib/games
 export ExecDir  = /libexec
 
+override_dh_auto_build-arch:
+       dh_auto_build -- stdai c-evo-dh-qt5
+
 override_dh_auto_build-indep:
        # Nothing to do here
 
@@ -25,6 +28,7 @@
        make install-data
 
 override_dh_auto_install-arch:
+       mv c-evo-dh-qt5 c-evo-dh-gtk2
        make install-binary
 
 #Override dh_strip to preserve line numbers in stack trace

Reply via email to