<div dir="ltr"><div class="gmail_default" style="font-size:small">In reviewing this thread of 32 notes, I was looking for anything that could be included in the manual to help in building a custom version. However, I think that the current statements of:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_default" style="font-size:small">1) Getting a build to work in a custom environment is not easy.</div><div class="gmail_default" style="font-size:small"> 2) 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.</div></blockquote><div class="gmail_default" style="font-size:small">says it all. Did anyone else note something that is important to help?<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Sep 19, 2024 at 10:52 AM Terje J. Hanssen via Cin <<a href="mailto:cin@lists.cinelerra-gg.org">cin@lists.cinelerra-gg.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div>
If my understanding is correct, the standard pre-built CinGG
packages are static binaries with all required thirdparty, ffmpeg
and libs included(?)<br>
<br>
Would it be possible to combine static and dynamic in one pre-built
so that users via setting could select what they want, ffmpeg and
libs included or from the system?<br>
Or is two different pre-builts required?<br>
<br>
Experiences with the latter?<br>
<br>
---------<br>
Refer to extracted sections from the CinGG manual Chapter 1 -
Installation below:<br>
<br>
If you prefer to not have to take the time to build CINELERRA-GG
Infinity yourself,<br>
there are pre-built dynamic or static binaries for various versions
of Ubuntu, Mint,<br>
Suse, Fedora, Debian ........<br>
<br>
The pkgs directory contains the standard packaged application for
various distros.<br>
This will install a dynamic system version for users who prefer to
have the binaries<br>
in the system area<br>
---------<br>
<br>
Notes about Building from Git in your Customized Environment<br>
<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>
./confgure --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>
..........<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" 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" 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">./confgure
--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</font><br>
<br>
<br>
<br>
<br>
</div>
-- <br>
Cin mailing list<br>
<a href="mailto:Cin@lists.cinelerra-gg.org" target="_blank">Cin@lists.cinelerra-gg.org</a><br>
<a href="https://lists.cinelerra-gg.org/mailman/listinfo/cin" rel="noreferrer" target="_blank">https://lists.cinelerra-gg.org/mailman/listinfo/cin</a><br>
</blockquote></div>