Hello, all! I was re-visiting those anylinux appimages suggested some time ago, and I made test appimage from qemu-system-ppc64 fork (you probably need -L to point it to keymaps and such, and -bios to point it to openbios-ppc build,specific to this fork) https://drive.google.com/drive/folders/1IBj91aP-mqZ8O2Hwjh6QjkBOGFhoYBFt?usp... I wonder if Andrea,as our long time Arch user can make experimental Appimage of classic cingg, so we can test it on variety of systems? https://github.com/pkgforge-dev/Anylinux-AppImages/blob/main/HOW-TO-MAKE-THE... Of course if you have time/desire to test-run this workflow. My uneasiness comes from fact scrip downloads some prebuild libs and runtimes and appimagetool, too. May be run it in chroot/container/VM? I ran it in not so important chroot from flash drive ...
Hi Andrea, thanks for testing so thoroughly, this is exactly the kind of feedback I need. *Building from source:* the steps differ from CinGG. The Qt6 version builds with CMake, there is no autogen.sh, no configure and no thirdparty build. FFmpeg and the other libraries come from your system. To make it easy I added a build script. It checks what is needed, tells you which development packages are missing, then configures and compiles: |git clone https://git.cinelerra-gg.org/sam/cinelerra-gg-qt6.git| |cd cinelerra-gg-qt6| |cinelerra-5.1/tools/build_qt6.sh| |cinelerra-5.1/build/cinelerra/cin| Run it with --check first if you only want to see what is missing. You need GCC 13 or newer, CMake 3.22 or newer, Qt 6.8 and FFmpeg 7. If your Qt is not the one of the system, put QT_DIR=/path/to/Qt in front of the command. The program runs from the build directory, there is no install step. After a git pull just run the script again. The "Build" section of the README.md has the details. *Overlay filter:* I could not reproduce this one. The plugin code is CinGG's, unchanged. In my test it works when two video tracks share it: Overlay attached to the upper track, the same effect attached to the lower track as a shared effect, then "Multiply" or "Addition" in the Mode list. The Compositor picture changes right away. On a single track it does nothing, because the plugin needs two layers. Could you tell me how you set it up? How many tracks, attached as a shared effect or separately, and which mode? Then I can test exactly your case. *Trimming:* glad you like it. I noted that the grab zone at the edge is too narrow without zooming in. *OpenCV filters:* yes, these are new. Scene detection, temporal denoise, stabilize, face tracking, auto reframe, retimer and object mask. Treat them as experimental. *Sketcher:* it is planned. Sketcher, Crikey and Tracer read X11 events directly and have to be ported first. Titler is still missing too. Oil painting, Polar, Whirl, YUV and GreyCStoration were missing in your build and are back in the current one (CinGG-qt6-alpha-20261013). *Videoscope:* you are right, the button was missing in the new Viewer and Compositor. The current build has a scope panel instead: Window → Show Scopes, or "Scopes" in the context menu of the Viewer and the Compositor. It shows waveform, RGB parade, vectorscope and histograms, and you can dock it anywhere or put each scope into a panel of its own. The window of the Videoscope plugin that cannot be enlarged is still on my list. *Red drop-down lists:* found and fixed. The drop-down lists of the older plugin windows took a marker colour of the theme instead of the menu background. The current build has the fix. If you still see a red list somewhere, please tell me in which window. Sam Am 14.10.26 um 18:16 schrieb Andrew Randrianasulu via Cin:
Hello, all!
I was re-visiting those anylinux appimages suggested some time ago, and I made test appimage from qemu-system-ppc64 fork (you probably need -L to point it to keymaps and such, and -bios to point it to openbios-ppc build,specific to this fork)
https://drive.google.com/drive/folders/1IBj91aP-mqZ8O2Hwjh6QjkBOGFhoYBFt?usp...
I wonder if Andrea,as our long time Arch user can make experimental Appimage of classic cingg, so we can test it on variety of systems?
https://github.com/pkgforge-dev/Anylinux-AppImages/blob/main/HOW-TO-MAKE-THE...
Of course if you have time/desire to test-run this workflow.
My uneasiness comes from fact scrip downloads some prebuild libs and runtimes and appimagetool, too.
May be run it in chroot/container/VM?
I ran it in not so important chroot from flash drive ...
_______________________________________________ Cin mailing list --cin@lists.cinelerra-gg.org To unsubscribe send an email tocin-leave@lists.cinelerra-gg.org
Hi Andrew, thanks for the pointer and for the test build. Anylinux looks like a good fit for the Qt6 AppImage too. The current one takes glibc from the host and needs glibc 2.38 or newer, so it will not start on older systems like Debian 12 or Ubuntu 22.04. Bundling glibc the way sharun does would fix exactly that. I'd like to try it once my current work is done: package the existing Qt6 build with quick-sharun and test it on a few distributions. I share your caution about the script downloading prebuilt parts, so I'll run it in a container. One question: have you packed a Qt6 application this way? In the Qt6 AppImage I take fontconfig and freetype from the host on purpose, because a bundled fontconfig could not parse the font configuration of newer distributions. I'd like to know whether Anylinux handles that. Sam Am 14.10.26 um 18:16 schrieb Andrew Randrianasulu via Cin:
Hello, all!
I was re-visiting those anylinux appimages suggested some time ago, and I made test appimage from qemu-system-ppc64 fork (you probably need -L to point it to keymaps and such, and -bios to point it to openbios-ppc build,specific to this fork)
https://drive.google.com/drive/folders/1IBj91aP-mqZ8O2Hwjh6QjkBOGFhoYBFt?usp...
I wonder if Andrea,as our long time Arch user can make experimental Appimage of classic cingg, so we can test it on variety of systems?
https://github.com/pkgforge-dev/Anylinux-AppImages/blob/main/HOW-TO-MAKE-THE...
Of course if you have time/desire to test-run this workflow.
My uneasiness comes from fact scrip downloads some prebuild libs and runtimes and appimagetool, too.
May be run it in chroot/container/VM?
I ran it in not so important chroot from flash drive ...
ср, 14 окт. 2026 г., 20:00 Sam via Cin <cin@lists.cinelerra-gg.org>:
Hi Andrew,
thanks for the pointer and for the test build. Anylinux looks like a good fit for the Qt6 AppImage too. The current one takes glibc from the host and needs glibc 2.38 or newer, so it will not start on older systems like Debian 12 or Ubuntu 22.04. Bundling glibc the way sharun does would fix exactly that.
I'd like to try it once my current work is done: package the existing Qt6 build with quick-sharun and test it on a few distributions. I share your caution about the script downloading prebuilt parts, so I'll run it in a container.
One question: have you packed a Qt6 application this way?
No, qemu used gtk3. I may try 86Box next (normally qt5, but can be compiled with qt6) , but not sure how well it may work in general (hopefully it will pick up roms from home directory if started as such appimage?) In the Qt6
AppImage I take fontconfig and freetype from the host on purpose, because a bundled fontconfig could not parse the font configuration of newer distributions. I'd like to know whether Anylinux handles that.
Sam
Am 14.10.26 um 18:16 schrieb Andrew Randrianasulu via Cin:
Hello, all!
I was re-visiting those anylinux appimages suggested some time ago, and I made test appimage from qemu-system-ppc64 fork (you probably need -L to point it to keymaps and such, and -bios to point it to openbios-ppc build,specific to this fork)
https://drive.google.com/drive/folders/1IBj91aP-mqZ8O2Hwjh6QjkBOGFhoYBFt?usp...
I wonder if Andrea,as our long time Arch user can make experimental Appimage of classic cingg, so we can test it on variety of systems?
https://github.com/pkgforge-dev/Anylinux-AppImages/blob/main/HOW-TO-MAKE-THE...
Of course if you have time/desire to test-run this workflow.
My uneasiness comes from fact scrip downloads some prebuild libs and runtimes and appimagetool, too.
May be run it in chroot/container/VM?
I ran it in not so important chroot from flash drive ...
_______________________________________________ Cin mailing list -- cin@lists.cinelerra-gg.org To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org
I tried to build an AppImage with AnyLinux, but, of course, I don't know how to proceed. I used the “script_anylinux.sh” script with my own modifications (I set the path to CinGG instead of the recommended “/usr/...”, etc. Compare with the example on GitHub ( https://github.com/pkgforge-dev/Anylinux-AppImages/blob/main/HOW-TO-MAKE-THE...)). The program crashes with the error listed in “sharun.txt.” I've tried using various paths for “.desktop,” but they all result in the same error. Any suggestions on how to use the environment variable in the .desktop file? Any other advice?
ср, 14 окт. 2026 г., 22:37 Andrea paz via Cin <cin@lists.cinelerra-gg.org>:
I tried to build an AppImage with AnyLinux, but, of course, I don't know how to proceed. I used the “script_anylinux.sh” script with my own modifications (I set the path to CinGG instead of the recommended “/usr/...”, etc. Compare with the example on GitHub ( https://github.com/pkgforge-dev/Anylinux-AppImages/blob/main/HOW-TO-MAKE-THE...)). The program crashes with the error listed in “sharun.txt.” I've tried using various paths for “.desktop,” but they all result in the same error. Any suggestions on how to use the environment variable in the .desktop file? Any other advice?
I used quick_sharun.sh script directly from program (qemu) folder. Without any arguments, just path to executable in build/ subfolder. It first complained tht .desctop file was missing, I copied qemu.desktop from Anylinux qemu example into AppDir already created by script, and set my executable there (qemu-system-ppc64 instead of qemu-system_x86-64). then it fully created AppDir and by re-running it as ./quick_sharun.sh --make-appimage it did create appimage in current folder for me ... May be our .desktop is formatted in some old/odd way? I'll try next in Debian 11 VM where I already have cingg compiled. _______________________________________________
Cin mailing list -- cin@lists.cinelerra-gg.org To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org
On Wed, Oct 14, 2026 at 11:01 PM Andrew Randrianasulu <randrianasulu@gmail.com> wrote:
ср, 14 окт. 2026 г., 22:37 Andrea paz via Cin <cin@lists.cinelerra-gg.org>:
I tried to build an AppImage with AnyLinux, but, of course, I don't know how to proceed. I used the “script_anylinux.sh” script with my own modifications (I set the path to CinGG instead of the recommended “/usr/...”, etc. Compare with the example on GitHub (https://github.com/pkgforge-dev/Anylinux-AppImages/blob/main/HOW-TO-MAKE-THE...)). The program crashes with the error listed in “sharun.txt.” I've tried using various paths for “.desktop,” but they all result in the same error. Any suggestions on how to use the environment variable in the .desktop file? Any other advice?
I used quick_sharun.sh script directly from program (qemu) folder. Without any arguments, just path to executable in build/ subfolder. It first complained tht .desctop file was missing, I copied qemu.desktop from Anylinux qemu example into AppDir already created by script, and set my executable there (qemu-system-ppc64 instead of qemu-system_x86-64).
then it fully created AppDir and by re-running it as
./quick_sharun.sh --make-appimage
it did create appimage in current folder for me ...
May be our .desktop is formatted in some old/odd way?
I'll try next in Debian 11 VM where I already have cingg compiled.
Hm. qemu.desktop looks like this [Desktop Entry] Name=QEMU Exec=qemu-system-ppc64 Icon=qemu StartupWMClass=qemu Comment="A generic and open source machine & userspace emulator and virtualizer" Type=Application Terminal=false Keywords=Emulator;Virtualization;KVM; Categories=System; X-AppImage-Name=QEMU X-AppImage-Version=UNKNOWN X-AppImage-Arch=x86_64 we miss StartupWMClass and X-Appimage lines But quick_sharun.sh created AppDir in 2 Gb RAM VM, problem is .. mkdwarfs just quits with "-1" at around 34% done :( May be 2Gb is too small ?
_______________________________________________ Cin mailing list -- cin@lists.cinelerra-gg.org To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org
On Thu, Oct 15, 2026 at 12:08 AM Andrew Randrianasulu <randrianasulu@gmail.com> wrote:
On Wed, Oct 14, 2026 at 11:01 PM Andrew Randrianasulu <randrianasulu@gmail.com> wrote:
ср, 14 окт. 2026 г., 22:37 Andrea paz via Cin <cin@lists.cinelerra-gg.org>:
I tried to build an AppImage with AnyLinux, but, of course, I don't know how to proceed. I used the “script_anylinux.sh” script with my own modifications (I set the path to CinGG instead of the recommended “/usr/...”, etc. Compare with the example on GitHub (https://github.com/pkgforge-dev/Anylinux-AppImages/blob/main/HOW-TO-MAKE-THE...)). The program crashes with the error listed in “sharun.txt.” I've tried using various paths for “.desktop,” but they all result in the same error. Any suggestions on how to use the environment variable in the .desktop file? Any other advice?
I used quick_sharun.sh script directly from program (qemu) folder. Without any arguments, just path to executable in build/ subfolder. It first complained tht .desctop file was missing, I copied qemu.desktop from Anylinux qemu example into AppDir already created by script, and set my executable there (qemu-system-ppc64 instead of qemu-system_x86-64).
then it fully created AppDir and by re-running it as
./quick_sharun.sh --make-appimage
it did create appimage in current folder for me ...
May be our .desktop is formatted in some old/odd way?
I'll try next in Debian 11 VM where I already have cingg compiled.
Hm.
qemu.desktop looks like this
[Desktop Entry] Name=QEMU Exec=qemu-system-ppc64 Icon=qemu StartupWMClass=qemu Comment="A generic and open source machine & userspace emulator and virtualizer" Type=Application Terminal=false Keywords=Emulator;Virtualization;KVM; Categories=System; X-AppImage-Name=QEMU X-AppImage-Version=UNKNOWN X-AppImage-Arch=x86_64
we miss StartupWMClass
and X-Appimage
lines
But quick_sharun.sh created AppDir in 2 Gb RAM VM, problem is ..
mkdwarfs just quits with "-1" at around 34% done :(
May be 2Gb is too small ?
for qt6 build of 86Box I see those warnings: ------------------------------------------------------------ WARNING: Qt was deployed but there is no kvantum plugin! This means the application will lack proper theme support! Install the packages that provide theme support before deploying In archlinux those are: qt6ct kvantum lxqt-qtplugin ------------------------------------------------------------ ------------------------------------------------------------ WARNING: Qt was deployed but there is no qtlxqt plugin! This means the application will lack proper theme support! Install the packages that provide theme support before deploying In archlinux those are: qt6ct kvantum lxqt-qtplugin ------------------------------------------------------------ ------------------------------------------------------------ WARNING: Qt was deployed but there is no qt6ct plugin! This means the application will lack proper theme support! Install the packages that provide theme support before deploying In archlinux those are: qt6ct kvantum lxqt-qtplugin ------------------------------------------------------------ ------------------------------------------------------------ ------------------------------------------------------------ WARNING: Detected the bundled libgallium links to libLLVM.so! libgallium only needs libLLVM for llvmpipe, which is a software rasterizer that is basically never used, softpipe can be used instead and does not need LLVM and people normally have GPUs and do not any of this to begin with!!! Sou you are adding a +100 MiB library in the application for nothing!!! Even worse, you cannot simply bundle libgallium from any linux distribution because the radeonsi driver often needs relative new versions of the linux kernel to work, see: https://github.com/pkgforge-dev/Anylinux-AppImages/issues/640#issuecomment-4... Instead use our builds of mesa which have no LLVM dependency and work on older kernels as well * https://github.com/pkgforge-dev/archlinux-pkgs-debloated * https://github.com/pkgforge-dev/Anylinux-AppImages/blob/main/useful-tools/ge... ------------------------------------------------------------ ------------------------------------------------------------ ------------------------------------------------------------ All done! Time taken: 0m 57s But it builds ..using more than 2 Gb of ram, lol.
_______________________________________________ Cin mailing list -- cin@lists.cinelerra-gg.org To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org
On Thu, Oct 15, 2026 at 12:23 AM Andrew Randrianasulu <randrianasulu@gmail.com> wrote:
On Thu, Oct 15, 2026 at 12:08 AM Andrew Randrianasulu <randrianasulu@gmail.com> wrote:
On Wed, Oct 14, 2026 at 11:01 PM Andrew Randrianasulu <randrianasulu@gmail.com> wrote:
ср, 14 окт. 2026 г., 22:37 Andrea paz via Cin <cin@lists.cinelerra-gg.org>:
I tried to build an AppImage with AnyLinux, but, of course, I don't know how to proceed. I used the “script_anylinux.sh” script with my own modifications (I set the path to CinGG instead of the recommended “/usr/...”, etc. Compare with the example on GitHub (https://github.com/pkgforge-dev/Anylinux-AppImages/blob/main/HOW-TO-MAKE-THE...)). The program crashes with the error listed in “sharun.txt.” I've tried using various paths for “.desktop,” but they all result in the same error. Any suggestions on how to use the environment variable in the .desktop file? Any other advice?
I used quick_sharun.sh script directly from program (qemu) folder. Without any arguments, just path to executable in build/ subfolder. It first complained tht .desctop file was missing, I copied qemu.desktop from Anylinux qemu example into AppDir already created by script, and set my executable there (qemu-system-ppc64 instead of qemu-system_x86-64).
then it fully created AppDir and by re-running it as
./quick_sharun.sh --make-appimage
it did create appimage in current folder for me ...
May be our .desktop is formatted in some old/odd way?
I'll try next in Debian 11 VM where I already have cingg compiled.
Hm.
qemu.desktop looks like this
[Desktop Entry] Name=QEMU Exec=qemu-system-ppc64 Icon=qemu StartupWMClass=qemu Comment="A generic and open source machine & userspace emulator and virtualizer" Type=Application Terminal=false Keywords=Emulator;Virtualization;KVM; Categories=System; X-AppImage-Name=QEMU X-AppImage-Version=UNKNOWN X-AppImage-Arch=x86_64
we miss StartupWMClass
and X-Appimage
lines
But quick_sharun.sh created AppDir in 2 Gb RAM VM, problem is ..
mkdwarfs just quits with "-1" at around 34% done :(
May be 2Gb is too small ?
for qt6 build of 86Box I see those warnings:
------------------------------------------------------------ WARNING: Qt was deployed but there is no kvantum plugin! This means the application will lack proper theme support! Install the packages that provide theme support before deploying In archlinux those are: qt6ct kvantum lxqt-qtplugin ------------------------------------------------------------ ------------------------------------------------------------ WARNING: Qt was deployed but there is no qtlxqt plugin! This means the application will lack proper theme support! Install the packages that provide theme support before deploying In archlinux those are: qt6ct kvantum lxqt-qtplugin ------------------------------------------------------------ ------------------------------------------------------------ WARNING: Qt was deployed but there is no qt6ct plugin! This means the application will lack proper theme support! Install the packages that provide theme support before deploying In archlinux those are: qt6ct kvantum lxqt-qtplugin ------------------------------------------------------------ ------------------------------------------------------------ ------------------------------------------------------------
WARNING: Detected the bundled libgallium links to libLLVM.so!
libgallium only needs libLLVM for llvmpipe, which is a software rasterizer that is basically never used, softpipe can be used instead and does not need LLVM and people normally have GPUs and do not any of this to begin with!!!
Sou you are adding a +100 MiB library in the application for nothing!!!
Even worse, you cannot simply bundle libgallium from any linux distribution because the radeonsi driver often needs relative new versions of the linux kernel to work, see: https://github.com/pkgforge-dev/Anylinux-AppImages/issues/640#issuecomment-4...
Instead use our builds of mesa which have no LLVM dependency and work on older kernels as well
* https://github.com/pkgforge-dev/archlinux-pkgs-debloated * https://github.com/pkgforge-dev/Anylinux-AppImages/blob/main/useful-tools/ge...
------------------------------------------------------------ ------------------------------------------------------------
------------------------------------------------------------ All done! Time taken: 0m 57s
But it builds ..using more than 2 Gb of ram, lol.
https://drive.google.com/drive/folders/13hIHKISQ9hMYA-hsJ8ML8uu-S6iQERP-?usp... Should be my 86Box git build. 165 Mb! But sound and video (including new Rage128 emulation) seems to be working with my Linux livecds
_______________________________________________ Cin mailing list -- cin@lists.cinelerra-gg.org To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org
I've tried several test, including adding “kvantum,” but I keep getting the same error. These are all just random attempts, because I don't really understand what I'm doing...
participants (3)
-
Andrea paz -
Andrew Randrianasulu -
Sam