<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">Den 19.09.2024 19:19, skrev Andrew
Randrianasulu:<br>
</div>
<blockquote type="cite"
cite="mid:CA+rFky60MkWUV5TxyO6v66hEHrrnoUe9st=HnhTz+7D_ryybUg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Sep 19, 2024 at
7:52 PM Terje J. Hanssen via Cin <<a
href="mailto:cin@lists.cinelerra-gg.org"
moz-do-not-send="true" class="moz-txt-link-freetext">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">
<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>
</div>
</blockquote>
<div><br>
</div>
<div>well, in general you can't link both statically (piece
of library embedded into binary) and shared (piece of code
loaded on demand or at launch). There might be some sort of
thunks/shims/wrappers dynamically dispatching calls to
external library if present (like firefox vs ffmpeg) but I
am not programmist enough for making this happen even for
most obvious vaapi libs.<br>
<br>
sorry.</div>
</div>
</div>
</blockquote>
<br>
I had "a little hope" something could be done via a
configuration/startup file :)<br>
<br>
In addition to the last sections below (from 1.3.3 in the manual):<br>
"just include "–without-thirdparty" to your configure script, "and
auto means probe and use the system version"<br>
<br>
<br>
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>
Is there available a built-guide or possible to list the detailed
procedure steps doing this? ;)<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CA+rFky60MkWUV5TxyO6v66hEHrrnoUe9st=HnhTz+7D_ryybUg@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div> </div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div> <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" moz-do-not-send="true">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"
moz-do-not-send="true">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"
moz-do-not-send="true" class="moz-txt-link-freetext">Cin@lists.cinelerra-gg.org</a><br>
<a
href="https://lists.cinelerra-gg.org/mailman/listinfo/cin"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.cinelerra-gg.org/mailman/listinfo/cin</a><br>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>