ср, 11 февр. 2026 г., 22:51 Terje J. Hanssen <[email protected]>:
On 2/11/26 6:35 PM, Andrew Randrianasulu wrote:
ср, 11 февр. 2026 г., 20:28 Terje J. Hanssen <[email protected]>:
On 2/11/26 3:52 PM, Andrew Randrianasulu wrote:
ср, 11 февр. 2026 г., 17:46 Terje J. Hanssen <[email protected]>:
On 2/11/26 2:48 PM, Terje J. Hanssen wrote:
On 2/11/26 2:32 PM, Andrew Randrianasulu wrote:
...........snip
--------------
8) Build procedure further from here?
Where does the bld_dynamic.sh script fit in?
./configure --with-single-user --disable-static-build --without-thirdparty
(there are some typos in the manual: "confgure" instead of "configure" pdf page 12, 13. 653)
setting CFLAGS?
should not be necessary, but you can try and see if it fails :)
I think --with-single-user is safer, and you can use
bld_appimage.sh
for appimage-ing result of (hopefully successful) compilation.
Note, I did not tried this with dynamic cingg build ... Hopefully appimagetool will only add loaders and not whole .. hw driver stack.
I think blds/bld_dynamic.sh is maintainer script more than user script
It was not updated to new git protocol (https vs git)
So you probably can skip it and just manually use your "--without-thirdparty --with-single-user --disable-static-build" configure line, and then make and make install
test and appimage it
Or possibly a configure line like this to include link to my system ffmpeg?
"--without-thirdparty --with-single-user --disable-static-build --with-ffmpeg=/usr/bin/ffmpeg"
or possibly?
./configure --with-single-user --disable-static-build --without-thirdparty --without-libdpx --with-external-ffmpeg
or alternatively (not sure about what is valid syntax) ?
./configure --with-single-user --disable-static-build --without-thirdparty --without-libdpx --with-systeml-ffmpeg
A Quick Comparison from Google/ai tells (does not need to be correct):
--with-external-ffmpeg Uses the specific FFmpeg version bundled in the Cinelerra thirdparty/ directory. --with-system-ffmpeg Uses the FFmpeg libraries already installed on your OS
you can use configure --help to see supported arguments.
Yeah, but unhappily it won't work here:
cd /home3/cinelerra/cinelerra-5.1 #
./configure --help -bash: ./configure: No such file or directory
where is it? My thought was that "configure" isn't executable (yet)?
It does not exist yet.
Run ./autogen.sh and it will hopefully generate it from configure.ac
Issue with ./autogen.sh and ./configure which worked earlier on Slowroll. Tried to install dh-autoreconf, but this didn't solve it
# cd /home3/cinelerra/cinelerra-5.1
./autogen.sh + rm -f global_config configure Makefile Makefile.in + rm -f aclocal.m4 depcomp compile install-sh ltmain.sh + rm -f config.log config.guess config.h config.h.in config.sub config.status missing + rm -rf autom4te.cache m4 + '[' '' = clean ']' + mkdir m4 + autoreconf --install ./autogen.sh: line 12: autoreconf: command not found ++ uname -o + '[' GNU/Linux = Android ']' + '[' -e /system/bin/app_process ']'
# zypper se autoreconf
Try *just* autoconf ? dh is some Debian helper, not sure what it supposed to do on Suse .....
| dh-autoreconf | Add-on for debhelper to call autoreconf and clean up after the build | package
# zypper in dh-autoreconf
Resolving package dependencies...
The following 2 recommended packages were automatically selected: perl-Archive-Cpio perl-File-FcntlLock
The following 7 NEW packages are going to be installed: debhelper dh-autoreconf dpkg perl-Archive-Cpio perl-Archive-Zip perl-File-FcntlLock strip-nondeterminism
ls -la *sh configure* -rwxr-xr-x. 1 root root 408 Feb 10 23:13 autogen.sh -rwxr-xr-x. 1 root root 3584 Feb 10 23:13 bld_appimage.sh -rwxr-xr-x. 1 root root 536 Feb 10 23:13 bld.sh -rw-r--r--. 1 root root 44376 Feb 10 23:13 configure.ac -rwxr-xr-x. 1 root root 310 Feb 10 23:13 inst.sh
The closest chmod 755 configure.ac ls -la configure* -rwxr-xr-x. 1 root root 44376 Feb 10 23:13 configure.ac
./configure --help -bash: ./configure: No such file or directory
./configure.ac --help ./configure.ac: line 2: syntax error near unexpected token `[2.69]' ./configure.ac: line 2: `AC_PREREQ([2.69])'
----------------
Further, I've tried to compare with what were suggested for my earlier build, and try to figure out if here are two procedures/scripts to follow and what is the difference:
Andrew replied:
https://lists.cinelerra-gg.org/archives/list/[email protected]/mess...
2) - cd to directory where ./autogen.sh located. 2a - set additional environment variables if you need so via export command 3) run ./autogen.sh 4) run ./configure with all switches you need. (for first try probably --with-single-user so build will be user-local, no need for installing into system)
my current build uses "./configure --with-single-user --with-git-ffmpeg= https://git.ffmpeg.org/ffmpeg.git"
but ffmpeg.git can be broken at any time by ffmpeg development process :(
5) run make 6) if doing single user build also run make install 7) run it from same directory as bin/cin (you can "ls bin" just to see if all files were build/installed)
MatN replied:
https://lists.cinelerra-gg.org/archives/list/[email protected]/mess...
You need to do cd /home/cinelerra/cinelerra-5.1 Then run "blds/bld_prepare.sh <os>" , where <os> is your os,
run blds/bld_prepare.sh without argument to get a list of OS-ses. This installs the needed development packages for your OS.
then (still in /home/cinelerra/cinelerra-5.1):
in bld.sh, change the config options to what you want.
./bld.sh (if not making an AppImage)
At first look, the latter seems simpler with fewer steps if it works here; comments +/- ?
Well, I just tried to be a bit extra verbose, and spell out changes we needed back then for enabling openvpl and stuff (now it should be just configure switch).
----------------
I had idea about adding configure switch (in addition to env variable?) to pick up libav* libs from standard location, but this idea only lives in my head for now.
_________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]