bld_appimage.sh modded to accept CONFIG_OPTIONS env. variable
Just file, not patch I tested it like CONFIG_OPTIONS="--without-thirdparty" ./bld_appimage.sh and it seems to work (not sure what will happen if you pass both --disable-static-build and --enable-static-build. I moved --enable-static-build to its own line so you hopefully can just harmlessly comment it out.)
Just file, not patch
I tested it like
CONFIG_OPTIONS="--without-thirdparty" ./bld_appimage.sh
and it seems to work (not sure what will happen if you pass both --disable-static-build and --enable-static-build. I moved --enable-static-build to its own line so you hopefully can just harmlessly comment it out.)
Since this is completely different then what is in the GIT source, is it what we should go with? My biggest concern is "makeimage" versus "linuxdeploy" and simplistically. This one has the advantage of adding the Manual documentation. But it is easy enough to add the Manual documentation AND this patch to the current GIT one: 0003-Add-CONFIG_OPTIONS-env.-variable-handling-to-bld_app.patch
пт, 20 февр. 2026 г., 02:03 Phyllis Smith <[email protected]>:
Just file, not patch
I tested it like
CONFIG_OPTIONS="--without-thirdparty" ./bld_appimage.sh
and it seems to work (not sure what will happen if you pass both --disable-static-build and --enable-static-build. I moved --enable-static-build to its own line so you hopefully can just harmlessly comment it out.)
Since this is completely different then what is in the GIT source, is it what we should go with? My biggest concern is "makeimage" versus "linuxdeploy" and simplistically. This one has the advantage of adding the Manual documentation.
But it is easy enough to add the Manual documentation AND this patch to the current GIT one: 0003-Add-CONFIG_OPTIONS-env.-variable-handling-to-bld_app.patch
Git patch was (hopefully) just this - diff between what we have there in root of cinelerra-5.1 tree (there is another script in blds/ directory! but with same name. they are different!) and my changes. If you want to mod script in blds with same $CONFIG_OPTIONS handling - go ahead, you have linuxdeploy working at least on slightly older OSes. (we ab/use appimage as some way to fossilize current build so we can easily retest even if os libs all slip away. Idea behind appimages was building on oldest possible OS of course)
On 20/02/2026 00:22, Andrew Randrianasulu wrote:
пт, 20 февр. 2026 г., 02:03 Phyllis Smith <[email protected]>:
Just file, not patch
I tested it like
CONFIG_OPTIONS="--without-thirdparty" ./bld_appimage.sh
and it seems to work (not sure what will happen if you pass both --disable-static-build and --enable-static-build. I moved --enable-static-build to its own line so you hopefully can just harmlessly comment it out.)
Since this is completely different then what is in the GIT source, is it what we should go with? My biggest concern is "makeimage" versus "linuxdeploy" and simplistically. This one has the advantage of adding the Manual documentation.
But it is easy enough to add the Manual documentation AND this patch to the current GIT one: 0003-Add-CONFIG_OPTIONS-env.-variable-handling-to-bld_app.patch
Git patch was (hopefully) just this - diff between what we have there in root of cinelerra-5.1 tree (there is another script in blds/ directory! but with same name. they are different!) and my changes.
If you want to mod script in blds with same $CONFIG_OPTIONS handling - go ahead, you have linuxdeploy working at least on slightly older OSes. (we ab/use appimage as some way to fossilize current build so we can easily retest even if os libs all slip away. Idea behind appimages was building on oldest possible OS of course)
In blds there are bld_static.sh and bld_dynamic.sh. Wouldn't it correspondingly be an idea to have bld_appimage_static.sh and bld_appimage_dynamic.sh? As standard the static version (standalone, single-user, bundled) might embed everything needed included the thirdbarty ffmpeg. The dynamic version (lightweight, single-user, unbundled) might as standard be based on the system ffmpeg and libs. Both could be customized by uncommenting options. --------- I have rebuild Cingg unbundled as previously on Slowroll using CFLAGS=-I/usr/include/ffmpeg ./configure --with-single-user --disable-static-build --without-thirdparty --without-libdpx Should then build a corresponding AppImage and applied the modded appimage.sh with line 20 commented out # CONFIG_OPTIONS="$CONFIG_OPTIONS --enable-static-build" CONFIG_OPTIONS="--without-thirdparty" ./bld_appimage.sh > bld_appimage.log 2>&1 I wonder why the dependice errors *) and stop arise, causing no AppImage created? Seemingly I have the claimed dependices installed, so I wonder if a CFLAG equivalent is needed or? 1) Checked the log tail bld_appimage.log Deploying dependencies for ELF file AppDir/usr/bin/zmpeg3show Deploying dependencies for ELF file AppDir/usr/bin/zmpeg3toc Deploying dependencies for ELF file AppDir/usr/bin/zmpeg3ifochk Deploying dependencies for ELF file AppDir/usr/bin/cin -- Deploying executables -- Deploying executable bin/cin WARNING: Could not find copyright files for file bin/cin using dpkg-query Deploying dependencies for ELF file bin/cin ERROR: No such file or directory: bin/mpeg2enc 2) Checked the config cat bld_appimage.log | grep -i configure configure script options are --without-thirdparty --with-single-user --with-booby 3) Checked for errors cat bld_appimage.log | grep -i error * checking for pulse/error.h... yes I have already libpulse-devel v. 17.0-6.1 installed ------/usr/include/pulse/error.h * Deploying shared library /lib64/libsamba-errors.so.1 WARNING: Could not find copyright files for file /lib64/libsamba-errors.so.1 using dpkg-query I have already samba-client-libs 4.23.5+git installed ------/usr/lib64/libsamba-errors.so.1 * ERROR: No such file or directory: bin/mpeg2enc I have already mjpegtools installed: which mpeg2enc /usr/bin/mpeg2enc
сб, 21 февр. 2026 г., 13:06 Terje J. Hanssen <[email protected]>:
On 20/02/2026 00:22, Andrew Randrianasulu wrote:
пт, 20 февр. 2026 г., 02:03 Phyllis Smith <[email protected]>:
Just file, not patch
I tested it like
CONFIG_OPTIONS="--without-thirdparty" ./bld_appimage.sh
and it seems to work (not sure what will happen if you pass both --disable-static-build and --enable-static-build. I moved --enable-static-build to its own line so you hopefully can just harmlessly comment it out.)
Since this is completely different then what is in the GIT source, is it what we should go with? My biggest concern is "makeimage" versus "linuxdeploy" and simplistically. This one has the advantage of adding the Manual documentation.
But it is easy enough to add the Manual documentation AND this patch to the current GIT one: 0003-Add-CONFIG_OPTIONS-env.-variable-handling-to-bld_app.patch
Git patch was (hopefully) just this - diff between what we have there in root of cinelerra-5.1 tree (there is another script in blds/ directory! but with same name. they are different!) and my changes.
If you want to mod script in blds with same $CONFIG_OPTIONS handling - go ahead, you have linuxdeploy working at least on slightly older OSes. (we ab/use appimage as some way to fossilize current build so we can easily retest even if os libs all slip away. Idea behind appimages was building on oldest possible OS of course)
In blds there are bld_static.sh and bld_dynamic.sh. Wouldn't it correspondingly be an idea to have bld_appimage_static.sh and bld_appimage_dynamic.sh? As standard the static version (standalone, single-user, bundled) might embed everything needed included the thirdbarty ffmpeg. The dynamic version (lightweight, single-user, unbundled) might as standard be based on the system ffmpeg and libs. Both could be customized by uncommenting options.
---------
I have rebuild Cingg unbundled as previously on Slowroll using
CFLAGS=-I/usr/include/ffmpeg ./configure --with-single-user --disable-static-build --without-thirdparty --without-libdpx
Should then build a corresponding AppImage and applied the modded appimage.sh with line 20 commented out
# CONFIG_OPTIONS="$CONFIG_OPTIONS --enable-static-build"
CONFIG_OPTIONS="--without-thirdparty" ./bld_appimage.sh > bld_appimage.log 2>&1
You forgot to add --without-libdpx ?
I wonder why the dependice errors *) and stop arise, causing no AppImage created? Seemingly I have the claimed dependices installed, so I wonder if a CFLAG equivalent is needed or?
1) Checked the log
tail bld_appimage.log Deploying dependencies for ELF file AppDir/usr/bin/zmpeg3show Deploying dependencies for ELF file AppDir/usr/bin/zmpeg3toc Deploying dependencies for ELF file AppDir/usr/bin/zmpeg3ifochk Deploying dependencies for ELF file AppDir/usr/bin/cin
-- Deploying executables -- Deploying executable bin/cin WARNING: Could not find copyright files for file bin/cin using dpkg-query Deploying dependencies for ELF file bin/cin ERROR: No such file or directory: bin/mpeg2enc
2) Checked the config
cat bld_appimage.log | grep -i configure configure script options are --without-thirdparty --with-single-user --with-booby
3) Checked for errors
cat bld_appimage.log | grep -i error
* checking for pulse/error.h... yes
I have already libpulse-devel v. 17.0-6.1 installed ------/usr/include/pulse/error.h
* Deploying shared library /lib64/libsamba-errors.so.1 WARNING: Could not find copyright files for file /lib64/libsamba-errors.so.1 using dpkg-query
I have already samba-client-libs 4.23.5+git installed ------/usr/lib64/libsamba-errors.so.1
* ERROR: No such file or directory: bin/mpeg2enc
I have already mjpegtools installed:
which mpeg2enc /usr/bin/mpeg2enc
Strage. you build from git, right? Maybe I broke install for this case? makeappimage look for binaries as instructed by -e switches, so file it looks for must be in bin directory relative to where you ran script (root of cinelerra-5.1 directory). It will add libraries from system locations ...
сб, 21 февр. 2026 г., 14:55 Andrew Randrianasulu <[email protected]>:
сб, 21 февр. 2026 г., 13:06 Terje J. Hanssen <[email protected]>:
On 20/02/2026 00:22, Andrew Randrianasulu wrote:
пт, 20 февр. 2026 г., 02:03 Phyllis Smith <[email protected]>:
Just file, not patch
I tested it like
CONFIG_OPTIONS="--without-thirdparty" ./bld_appimage.sh
and it seems to work (not sure what will happen if you pass both --disable-static-build and --enable-static-build. I moved --enable-static-build to its own line so you hopefully can just harmlessly comment it out.)
Since this is completely different then what is in the GIT source, is it what we should go with? My biggest concern is "makeimage" versus "linuxdeploy" and simplistically. This one has the advantage of adding the Manual documentation.
But it is easy enough to add the Manual documentation AND this patch to the current GIT one: 0003-Add-CONFIG_OPTIONS-env.-variable-handling-to-bld_app.patch
Git patch was (hopefully) just this - diff between what we have there in root of cinelerra-5.1 tree (there is another script in blds/ directory! but with same name. they are different!) and my changes.
If you want to mod script in blds with same $CONFIG_OPTIONS handling - go ahead, you have linuxdeploy working at least on slightly older OSes. (we ab/use appimage as some way to fossilize current build so we can easily retest even if os libs all slip away. Idea behind appimages was building on oldest possible OS of course)
In blds there are bld_static.sh and bld_dynamic.sh. Wouldn't it correspondingly be an idea to have bld_appimage_static.sh and bld_appimage_dynamic.sh? As standard the static version (standalone, single-user, bundled) might embed everything needed included the thirdbarty ffmpeg. The dynamic version (lightweight, single-user, unbundled) might as standard be based on the system ffmpeg and libs. Both could be customized by uncommenting options.
---------
I have rebuild Cingg unbundled as previously on Slowroll using
CFLAGS=-I/usr/include/ffmpeg ./configure --with-single-user --disable-static-build --without-thirdparty --without-libdpx
Should then build a corresponding AppImage and applied the modded appimage.sh with line 20 commented out
# CONFIG_OPTIONS="$CONFIG_OPTIONS --enable-static-build"
CONFIG_OPTIONS="--without-thirdparty" ./bld_appimage.sh > bld_appimage.log 2>&1
You forgot to add --without-libdpx ?
I wonder why the dependice errors *) and stop arise, causing no AppImage created? Seemingly I have the claimed dependices installed, so I wonder if a CFLAG equivalent is needed or?
1) Checked the log
tail bld_appimage.log Deploying dependencies for ELF file AppDir/usr/bin/zmpeg3show Deploying dependencies for ELF file AppDir/usr/bin/zmpeg3toc Deploying dependencies for ELF file AppDir/usr/bin/zmpeg3ifochk Deploying dependencies for ELF file AppDir/usr/bin/cin
-- Deploying executables -- Deploying executable bin/cin WARNING: Could not find copyright files for file bin/cin using dpkg-query Deploying dependencies for ELF file bin/cin ERROR: No such file or directory: bin/mpeg2enc
2) Checked the config
cat bld_appimage.log | grep -i configure configure script options are --without-thirdparty --with-single-user --with-booby
3) Checked for errors
cat bld_appimage.log | grep -i error
* checking for pulse/error.h... yes
I have already libpulse-devel v. 17.0-6.1 installed ------/usr/include/pulse/error.h
* Deploying shared library /lib64/libsamba-errors.so.1 WARNING: Could not find copyright files for file /lib64/libsamba-errors.so.1 using dpkg-query
I have already samba-client-libs 4.23.5+git installed ------/usr/lib64/libsamba-errors.so.1
* ERROR: No such file or directory: bin/mpeg2enc
I have already mjpegtools installed:
which mpeg2enc /usr/bin/mpeg2enc
Strage. you build from git, right? Maybe I broke install for this case?
makeappimage look for binaries as instructed by -e switches, so file it looks for must be in bin directory relative to where you ran script (root of cinelerra-5.1 directory). It will add libraries from system locations ...
On termux build with blds/termux_dyn.sh I have ~/cinelerra/cinelerra-5.1 $ ls -l bin | grep \\-rwx -rwx------. 1 u0_a204 u0_a204 120584 Feb 11 03:59 bdwrite -rwx------. 1 u0_a204 u0_a204 16756472 Feb 18 13:31 cin -rwx------. 1 u0_a204 u0_a204 454104 Feb 11 03:41 hveg2enc -rwx------. 1 u0_a204 u0_a204 1534960 Feb 11 03:59 lv2ui -rwx------. 1 u0_a204 u0_a204 1808368 Feb 11 04:06 mplexlo -rwx------. 1 u0_a204 u0_a204 1807264 Feb 11 04:06 zmpeg3cat -rwx------. 1 u0_a204 u0_a204 1816064 Feb 11 04:06 zmpeg3cc2txt -rwx------. 1 u0_a204 u0_a204 1771016 Feb 11 04:06 zmpeg3ifochk -rwx------. 1 u0_a204 u0_a204 1766280 Feb 11 04:06 zmpeg3show -rwx------. 1 u0_a204 u0_a204 1798592 Feb 11 04:06 zmpeg3toc so yes, you either need to edit makeappimage line and remove -e bin/mpeg2enc part, or copy script under different name (for example bld_appimage_dynamuc.sh as you suggested) and then edit it so it does not look for this file, mpeg2enc build as part of thirdparty/mjpegtools build. You probably also can try to put your system's mpeg2enc binary there manually and see if it works?
Just file, not patch
I tested it like
CONFIG_OPTIONS="--without-thirdparty" ./bld_appimage.sh
and it seems to work (not sure what will happen if you pass both --disable-static-build and --enable-static-build. I moved --enable-static-build to its own line so you hopefully can just harmlessly comment it out.)
Since this is completely different then what is in the GIT source, is it what we should go with? My biggest concern is "makeimage" versus "linuxdeploy" and simplistically. This one has the advantage of adding the Manual documentation.
But it is easy enough to add the Manual documentation AND this patch to the current GIT one: 0003-Add-CONFIG_OPTIONS-env.-variable-handling-to-bld_app.patch
Git patch was (hopefully) just this - diff between what we have there in root of cinelerra-5.1 tree (there is another script in blds/ directory! but with same name. they are different!) and my changes.
If you want to mod script in blds with same $CONFIG_OPTIONS handling - go ahead, you have linuxdeploy working at least on slightly older OSes. (we ab/use appimage as some way to fossilize current build so we can easily retest even if os libs all slip away. Idea behind appimages was building on oldest possible OS of course)
For now checked into GIT the patched versions of bld_appimage.sh and
blds/bld_prepare.sh. Can not remember why 2 versions of bld_appimage.s in the main directory and one in the blds directory but probably because of the usefulness of the main one and the simplistic one in the blds directory for me.
In blds there are bld_static.sh and bld_dynamic.sh. Wouldn't it correspondingly be an idea to have bld_appimage_static.sh and bld_appimage_dynamic.sh?
This is a good idea as presented by Terje so I am going to add this to Mantis Bug Tracker so it does not get lost. As standard the static version (standalone, single-user, bundled) might
embed everything needed included the thirdbarty ffmpeg. The dynamic version (lightweight, single-user, unbundled) might as standard be based on the system ffmpeg and libs. Both could be customized by uncommenting options.
participants (3)
-
Andrew Randrianasulu -
Phyllis Smith -
Terje J. Hanssen