bld_appimage.sh of unbundled build on openSUSE Slowroll (Tumbleweed)
Current Cingg unbundled build from Git on openSUSE Slowroll (Tumbleweed) using system FFMpeg-8 and libs, used this CFLAGS=-I/usr/include/ffmpeg ./configure --with-single-user --disable-static-build --without-thirdparty --without-libdpx Last time I build a similar AppImage in 2024 was with ffmpeg-7 when I used /Cin # sh ./bld_appimage.sh 2>&1 | tee bld_appimage.log Now opt 1) I want a minimum appimage for the unbundled build to run on identical Slowroll, ffmpeg and libs on other hardware. Will the bld_appimage.sh do it as is, possibly specific config line or other options? opt 2) The corresponding for a normal static build AppImage to run on all distributions and hardware
On 2/16/26 7:07 PM, Terje J. Hanssen wrote:
Current Cingg unbundled build from Git on openSUSE Slowroll (Tumbleweed) using system FFMpeg-8 and libs, used this CFLAGS=-I/usr/include/ffmpeg ./configure --with-single-user --disable-static-build --without-thirdparty --without-libdpx
Last time I build a similar AppImage in 2024 was with ffmpeg-7 when I used
/Cin # sh ./bld_appimage.sh 2>&1 | tee bld_appimage.log
Now
opt 1) I want a minimum appimage for the unbundled build to run on identical Slowroll, ffmpeg and libs on other hardware. Will the bld_appimage.sh do it as is, possibly specific config line or other options?
opt 2) The corresponding for a normal static build AppImage to run on all distributions and hardware
opt 3) Possibly a rpm package would be better for opt 1) Do we have a updated build script for this?
пн, 16 февр. 2026 г., 21:15 Terje J. Hanssen via Cin < [email protected]>:
On 2/16/26 7:07 PM, Terje J. Hanssen wrote:
Current Cingg unbundled build from Git on openSUSE Slowroll (Tumbleweed) using system FFMpeg-8 and libs, used this CFLAGS=-I/usr/include/ffmpeg ./configure --with-single-user --disable-static-build --without-thirdparty --without-libdpx
Last time I build a similar AppImage in 2024 was with ffmpeg-7 when I used
/Cin # sh ./bld_appimage.sh 2>&1 | tee bld_appimage.log
Now
opt 1) I want a minimum appimage for the unbundled build to run on identical Slowroll, ffmpeg and libs on other hardware. Will the bld_appimage.sh do it as is, possibly specific config line or other options?
It will re-run ./configure with its own options, but do not touch build in bin, so in my case it packaged what I previously build with custom ./configure
opt 2) The corresponding for a normal static build AppImage to run on all distributions and hardware
Probably same script but after you run make clean? Be sure to move previously created appimage out of dir.
opt 3) Possibly a rpm package would be better for opt 1) Do we have a updated build script for this?
I used rpmbuild with .spec file, but you might want to tweak it for downloading latest release, or git snapshot. rpmbuild -bb blds/cinelerra.spec
_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
On 2/16/26 8:11 PM, Andrew Randrianasulu wrote:
пн, 16 февр. 2026 г., 21:15 Terje J. Hanssen via Cin <[email protected]>:
On 2/16/26 7:07 PM, Terje J. Hanssen wrote: > Current Cingg unbundled build from Git on openSUSE Slowroll > (Tumbleweed) using system FFMpeg-8 and libs, used this > CFLAGS=-I/usr/include/ffmpeg ./configure --with-single-user > --disable-static-build --without-thirdparty --without-libdpx > > Last time I build a similar AppImage in 2024 was with ffmpeg-7 when I > used > > /Cin # sh ./bld_appimage.sh 2>&1 | tee bld_appimage.log > > Now > > opt 1) > I want a minimum appimage for the unbundled build to run on identical > Slowroll, ffmpeg and libs on other hardware. > Will the bld_appimage.sh do it as is, possibly specific config line or > other options?
It will re-run ./configure with its own options, but do not touch build in bin, so in my case it packaged what I previously build with custom ./configure
Unhappily it seemingly did just that ......? Now I can't launch bin/cin localhost:/Cin # ./bin/cin -bash: ./bin/cin: No such file or directory In my attempt to build an AppImage build I used the default bld_appimage.sh Does it really try to rebuild Cingg from scratch? # Build Cinelerra itself. ( ./autogen.sh ./configure $CONFIG_OPTIONS make && make install ) 2>&1 | tee log mv Makefile Makefile.cfg cp Makefile.devel Makefile ----------------- # cd /Cin ./bld_appimage.sh 2>&1 | tee bld_appimage.log tail appimage.log Deploying dependencies for ELF file AppDir/usr/bin/zmpeg3cat Deploying dependencies for ELF file AppDir/usr/bin/mplexlo Deploying dependencies for ELF file AppDir/usr/bin/hveg2enc Deploying dependencies for ELF file AppDir/usr/bin/bdwrite 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 executables -- ERROR: No such file or directory: bin/cin cat appimage.log | grep -i error Deploying shared library /lib64/libsamba-errors.so.1 WARNING: Could not find copyright files for file /lib64/libsamba-errors.so.1 using dpkg-query ERROR: No such file or directory: bin/cin The AppDir structure is there (partly), but because the build was broken there is no cin executeable in /Cin/AppDir/usr/bin
> > opt 2) > The corresponding for a normal static build AppImage to run on all > distributions and hardware
Probably same script but after you run make clean? Be sure to move previously created appimage out of dir.
> > opt 3) Possibly a rpm package would be better for opt 1) Do we have a updated build script for this?
I used rpmbuild with .spec file, but you might want to tweak it for downloading latest release, or git snapshot.
rpmbuild -bb blds/cinelerra.spec
> > > > > > > >
_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
вт, 17 февр. 2026 г., 19:55 Terje J. Hanssen <[email protected]>:
On 2/16/26 8:11 PM, Andrew Randrianasulu wrote:
пн, 16 февр. 2026 г., 21:15 Terje J. Hanssen via Cin < [email protected]>:
On 2/16/26 7:07 PM, Terje J. Hanssen wrote:
Current Cingg unbundled build from Git on openSUSE Slowroll (Tumbleweed) using system FFMpeg-8 and libs, used this CFLAGS=-I/usr/include/ffmpeg ./configure --with-single-user --disable-static-build --without-thirdparty --without-libdpx
Last time I build a similar AppImage in 2024 was with ffmpeg-7 when I used
/Cin # sh ./bld_appimage.sh 2>&1 | tee bld_appimage.log
Now
opt 1) I want a minimum appimage for the unbundled build to run on identical Slowroll, ffmpeg and libs on other hardware. Will the bld_appimage.sh do it as is, possibly specific config line or other options?
It will re-run ./configure with its own options, but do not touch build in bin, so in my case it packaged what I previously build with custom ./configure
Unhappily it seemingly did just that ......?
Now I can't launch bin/cin localhost:/Cin # ./bin/cin -bash: ./bin/cin: No such file or directory
In my attempt to build an AppImage build I used the default bld_appimage.sh
Does it really try to rebuild Cingg from scratch?
# Build Cinelerra itself. ( ./autogen.sh ./configure $CONFIG_OPTIONS make && make install ) 2>&1 | tee log mv Makefile Makefile.cfg cp Makefile.devel Makefile
-----------------
# cd /Cin ./bld_appimage.sh 2>&1 | tee bld_appimage.log
tail appimage.log Deploying dependencies for ELF file AppDir/usr/bin/zmpeg3cat Deploying dependencies for ELF file AppDir/usr/bin/mplexlo Deploying dependencies for ELF file AppDir/usr/bin/hveg2enc Deploying dependencies for ELF file AppDir/usr/bin/bdwrite 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 executables -- ERROR: No such file or directory: bin/cin
Sorry, I forgot if you used --with-single-user too? I used this for my build. Not sure why other binaries are there, but not main one :( At worst you can pass your switches as $CONFIG_OPTIONS (export CONFIG_OPTIONS= " -with-single-user --without-thirdparty --without-libdpx " before setting CFLAGS too, and running ./bld_appimage.sh , I think )
cat appimage.log | grep -i error Deploying shared library /lib64/libsamba-errors.so.1 WARNING: Could not find copyright files for file /lib64/libsamba-errors.so.1 using dpkg-query ERROR: No such file or directory: bin/cin
The AppDir structure is there (partly), but because the build was broken there is no cin executeable in /Cin/AppDir/usr/bin
opt 2) The corresponding for a normal static build AppImage to run on all distributions and hardware
Probably same script but after you run make clean? Be sure to move previously created appimage out of dir.
opt 3) Possibly a rpm package would be better for opt 1) Do we have a updated build script for this?
I used rpmbuild with .spec file, but you might want to tweak it for downloading latest release, or git snapshot.
rpmbuild -bb blds/cinelerra.spec
_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
вт, 17 февр. 2026 г., 21:25 Andrew Randrianasulu <[email protected]>:
вт, 17 февр. 2026 г., 19:55 Terje J. Hanssen <[email protected]>:
On 2/16/26 8:11 PM, Andrew Randrianasulu wrote:
пн, 16 февр. 2026 г., 21:15 Terje J. Hanssen via Cin < [email protected]>:
On 2/16/26 7:07 PM, Terje J. Hanssen wrote:
Current Cingg unbundled build from Git on openSUSE Slowroll (Tumbleweed) using system FFMpeg-8 and libs, used this CFLAGS=-I/usr/include/ffmpeg ./configure --with-single-user --disable-static-build --without-thirdparty --without-libdpx
Last time I build a similar AppImage in 2024 was with ffmpeg-7 when I used
/Cin # sh ./bld_appimage.sh 2>&1 | tee bld_appimage.log
Now
opt 1) I want a minimum appimage for the unbundled build to run on identical Slowroll, ffmpeg and libs on other hardware. Will the bld_appimage.sh do it as is, possibly specific config line or other options?
It will re-run ./configure with its own options, but do not touch build in bin, so in my case it packaged what I previously build with custom ./configure
Unhappily it seemingly did just that ......?
Now I can't launch bin/cin localhost:/Cin # ./bin/cin -bash: ./bin/cin: No such file or directory
In my attempt to build an AppImage build I used the default bld_appimage.sh
Does it really try to rebuild Cingg from scratch?
# Build Cinelerra itself. ( ./autogen.sh ./configure $CONFIG_OPTIONS make && make install ) 2>&1 | tee log mv Makefile Makefile.cfg cp Makefile.devel Makefile
-----------------
# cd /Cin ./bld_appimage.sh 2>&1 | tee bld_appimage.log
tail appimage.log Deploying dependencies for ELF file AppDir/usr/bin/zmpeg3cat Deploying dependencies for ELF file AppDir/usr/bin/mplexlo Deploying dependencies for ELF file AppDir/usr/bin/hveg2enc Deploying dependencies for ELF file AppDir/usr/bin/bdwrite 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 executables -- ERROR: No such file or directory: bin/cin
Sorry, I forgot if you used --with-single-user too? I used this for my build.
Not sure why other binaries are there, but not main one :(
At worst you can pass your switches as $CONFIG_OPTIONS (export CONFIG_OPTIONS= " -with-single-user --without-thirdparty --without-libdpx " before setting CFLAGS too, and running ./bld_appimage.sh , I think )
Ah, I looked into script and no, it does not append externally defined CONFIG_OPTIONS,so you either need to edit script with your parameters (may be comment out original line with # , so you will have reference) or edit script so it accept envr. variable. Probably just CONFIG_OPTIONS="$CONFIG_OPTIONS {other options }" as first CONFIG_OPTIONS line, instead of CONFIG_OPTIONS="--with-single-user --with-booby --enable-static-build"
cat appimage.log | grep -i error Deploying shared library /lib64/libsamba-errors.so.1 WARNING: Could not find copyright files for file /lib64/libsamba-errors.so.1 using dpkg-query ERROR: No such file or directory: bin/cin
The AppDir structure is there (partly), but because the build was broken there is no cin executeable in /Cin/AppDir/usr/bin
opt 2) The corresponding for a normal static build AppImage to run on all distributions and hardware
Probably same script but after you run make clean? Be sure to move previously created appimage out of dir.
opt 3) Possibly a rpm package would be better for opt 1) Do we have a updated build script for this?
I used rpmbuild with .spec file, but you might want to tweak it for downloading latest release, or git snapshot.
rpmbuild -bb blds/cinelerra.spec
_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
participants (2)
-
Andrew Randrianasulu -
Terje J. Hanssen