<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">вс, 22 сент. 2024 г., 13:56 Terje J. Hanssen via Cin <<a href="mailto:cin@lists.cinelerra-gg.org" target="_blank" rel="noreferrer">cin@lists.cinelerra-gg.org</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div>
After getting the generic built environment for Cingg on
openSUSE-Slowroll in place, it's time to continue with the steps to
get Cingg built from git using the system FFmpeg and libs.<br>
<br>
First a reference to and from the previous thread<br>
<a href="https://lists.cinelerra-gg.org/pipermail/cin/2024-September/008652.html" rel="noreferrer noreferrer" target="_blank">https://lists.cinelerra-gg.org/pipermail/cin/2024-September/008652.html</a><br>
<br>
----------------<br>
from the manual 1.3.8 Unbundled Builds<br>
"There are some generic build scripts included in the CINELERRA-GG
GIT repository<br>
for users who want to do unbundled builds with ffmpeg already
available on their<br>
system. This has been tested on Arch, Ubuntu 18, FreeBSD, Windows10
and Leap<br>
15 (rpm) at the time this was documented. The names of the build
scripts are:<br>
arch.bld, bsd.bld, deb.bld, rpm.bld, and cygwin.bld. These scripts
are in<br>
the blds subdirectory."<br>
<br>
from 1.3.3 in the manual):<br>
Notes about Building from Git in your Customized Environment<br>
Getting a build to work in a custom environment is not easy. If you
have already installed libraries which are normally in the
thirdparty build, getting them to be recognized means you have to
install the devel version so the header files which match the
library interfaces exist. If you want to build using only the
thirdparty libraries installed in your system, just include
"–without-thirdparty" to your configure script. For example:<br>
<br>
./configure --with-single-user --disable-static-build
--without-thirdparty<br>
<br>
Below is the list of thirdparty builds, but this list may have
changed over time.<br>
<br>
Table 1.1: List of thirdparty builds <br>
<blockquote><font face="Courier New, Courier, monospace">a52dec
yes</font><br>
<font face="Courier New, Courier, monospace">djbfft yes</font><br>
<font face="Courier New, Courier, monospace">ffmpeg yes</font><br>
<font face="Courier New, Courier, monospace">fftw auto</font><br>
<font face="Courier New, Courier, monospace">flac auto</font><br>
<font face="Courier New, Courier, monospace">giflib yes</font><br>
<font face="Courier New, Courier, monospace">ilmbase auto</font><br>
<font face="Courier New, Courier, monospace">lame auto</font><br>
<font face="Courier New, Courier, monospace">libavc1394 auto</font><br>
<font face="Courier New, Courier, monospace">libraw1394 auto</font><br>
<font face="Courier New, Courier, monospace">libiec61883 auto</font><br>
<font face="Courier New, Courier, monospace">libdv auto<br>
.......snip<br>
</font></blockquote>
The yes means force build and auto means probe and use the system
version if the build operation is not static. To get your customized
build to work, you need to change the probe options for the
conflicting libraries from yes to auto, or even rework the
<a href="http://configure.ac" rel="noreferrer noreferrer" target="_blank">configure.ac</a> script. There may be several libraries which need
special treatment.<br>
<br>
An example of a problem you might encounter with your customized
installation is with a52dec which has probes line
(CHECK_LIB/CHECK_HEADERS) in <a href="http://configure.ac" rel="noreferrer noreferrer" target="_blank">configure.ac</a>, but djbfft does not. In
this case, djbfft is only built because a52dec is built, so if your
system has a52dec, set a52dec to auto and see if that problem is
solved by retrying the build with:<br>
<br>
<font face="Courier New, Courier, monospace">./configure
--with-single-user -enable-a52dec=auto .</font><br>
<br>
With persistence, you can get results, but it may take several tries
to stabilize the build. If you need help, email the log and
config.log, which is usually sufficient to determine why a build
failed.<br>
<br>
If you have already installed the libfdk_aac development package on
your computer because you prefer this version over the default aac,
you will have to do the following to get this alternative
operational. The libfdk_aac library is not a part of CINELERRA-GG by
default because it is not license free.<br>
<br>
<font face="Courier New, Courier, monospace">export
FFMPEG_EXTRA_CFG=" --enable-libfdk-aac --enable-nonfree"<br>
export EXTRA_LIBS=" -lfdk-aac"<br>
for f in `grep -lw aac cinelerra-5.1/ffmpeg/audio/*`; do<br>
sed -e 's/\<aac\>/libfdk_aac/' -i $f<br>
done<br>
--------------<br>
<br>
FFmpeg from Packman (thirdparty for Slowroll) has the following
capabilities enabled and typical Hwaccel methods available:<br>
<br>
ffmpeg -hwaccels<br>
ffmpeg version 7.0 Copyright (c) 2000-2024 the FFmpeg developers<br>
built with gcc 14 (SUSE Linux)<br>
configuration: --prefix=/usr --libdir=/usr/lib64
--shlibdir=/usr/lib64 --incdir=/usr/include/ffmpeg
--extra-cflags='-O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3
-fstack-protector-strong -funwind-tables
-fasynchronous-unwind-tables -fstack-clash-protection
-Werror=return-type -flto=auto -ffat-lto-objects -g'
--optflags='-O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3
-fstack-protector-strong -funwind-tables
-fasynchronous-unwind-tables -fstack-clash-protection
-Werror=return-type -flto=auto -ffat-lto-objects -g'
--disable-htmlpages --enable-pic --disable-stripping
--enable-shared --disable-static --enable-gpl --enable-version3
--enable-libsmbclient --disable-openssl --enable-gnutls
--enable-ladspa --enable-libshaderc --enable-vulkan
--enable-libplacebo --enable-libaom --enable-libass
--enable-libbluray --enable-libbs2b --enable-libcdio
--enable-libcodec2 --enable-libdav1d --enable-libdc1394
--enable-libdrm --enable-libfontconfig --enable-libfreetype
--enable-libfribidi --enable-libgsm --enable-libjack
--enable-libjxl --enable-librist --enable-libmp3lame
--enable-libmysofa --enable-libopenjpeg --enable-libopenmpt
--enable-libopenh264-dlopen --enable-libopus --enable-libpulse
--enable-librav1e --enable-librubberband --enable-libsvtav1
--enable-libsoxr --enable-libspeex --enable-libssh --enable-libsrt
--enable-libtheora --enable-libtwolame --enable-libvidstab
--enable-libvmaf --enable-libvorbis --enable-libvpx
--enable-libwebp --enable-libxml2 --enable-libzimg --enable-libzmq
--enable-libzvbi --enable-lto --enable-lv2 --enable-libvpl
--enable-vaapi --enable-vdpau --enable-version3
--enable-libfdk-aac-dlopen --enable-nonfree
--enable-libopencore-amrnb --enable-libopencore-amrwb
--enable-libvo-amrwbenc --enable-libx264 --enable-libx265
--enable-libxvid<br>
libavutil 59. 8.100 / 59. 8.100<br>
libavcodec 61. 3.100 / 61. 3.100<br>
libavformat 61. 1.100 / 61. 1.100<br>
libavdevice 61. 1.100 / 61. 1.100<br>
libavfilter 10. 1.100 / 10. 1.100<br>
libswscale 8. 1.100 / 8. 1.100<br>
libswresample 5. 1.100 / 5. 1.100<br>
libpostproc 58. 1.100 / 58. 1.100<br>
Hardware acceleration methods:<br>
vdpau<br>
cuda<br>
vaapi<br>
qsv<br>
drm<br>
vulkan<br>
<br>
-------------------<br>
<br>
Suggestions to modified/additional procedure steps to build Cingg
from git using the system FFmpeg and libs<br>
continued from the previous thread?<br>
<a href="https://lists.cinelerra-gg.org/pipermail/cin/2024-September/008655.html" rel="noreferrer noreferrer" target="_blank">https://lists.cinelerra-gg.org/pipermail/cin/2024-September/008655.html</a><br>
<br>
</font></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">try</div><div dir="auto"><br></div><div dir="auto">./configure --with-single-user --disable-static-build --without-thirdparty --without-libdpx<br></div><div dir="auto"><br></div><div dir="auto">you might move just-build cingg+plugins in "bin" directory somewhere away in case you will want to make more tests with it, then run "make clean" configure line as above, make, make install</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><font face="Courier New, Courier, monospace"><br>
<br>
</font>
</div>
-- <br>
Cin mailing list<br>
<a href="mailto:Cin@lists.cinelerra-gg.org" rel="noreferrer noreferrer" target="_blank">Cin@lists.cinelerra-gg.org</a><br>
<a href="https://lists.cinelerra-gg.org/mailman/listinfo/cin" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.cinelerra-gg.org/mailman/listinfo/cin</a><br>
</blockquote></div></div></div>