#
How to Build CINELERRA-GG from Developer's Git Repository

These are generic build instructions for building CINELERRA-GG Infinity. Known to work on Ubuntu, Mint, OpenSuse, Fedora, Debian, Centos, Arch, Slackware, and Gentoo. Compiling from git is perhaps the best way to get CINELERRA-GG on 32-bit systems3. It has not been tested on every single possible distro yet so you might expect to have to make some minor changes. Also works on a somewhat limited basis on FreeBSD and Windows 10 with the bsd.patch for FreeBSD and the cygwin.patch for Windows 10. As of 10/31/2020, FreeBSD and Windows 10 builds and patches are no longer being maintained so that they will work using the GIT version in use at that time but you will have to create new patches for arising problems on later GITs.

NOTE: as of May 31, 2021 when Context Help was added, to include this Context Help you will need to download the corresponding tgz file containing the HTML manual sections referenced for the Help pages. The file to download is: `https://cinelerra-gg.org/download/images/HTML_Manual-20220131.tgz`substituting for "20220131" the "yyyymmdd" representing latest release date. Then unpack to your Cinelerra/bin/doc directory so it is included in your built system. NOTE End

Alternatively, there are some pre-built dynamic or static binaries which are updated on a fairly regular basis (as long as code changes have been made) available at the link below.

https://cinelerra-gg.org/download/

There are 2 kinds of builds, the default system-build and a single-user build. A system build has results which are installed to the system. The majority of the files are installed in the standard system paths, but some customization is possible. The single user build allows for running completely out of a local user directory so it doesn't affect the system.

We recommend the single-user version when possible. It makes it very easy to install a new version without having to delete the older version in case you want it for backup – once you are happy with the new version, all you have to do is delete the entire old directory path. Another reason for using single-user is that if you install a new Operating System version and if you have CINELERRA-GG on separate disk space that is preserved, you won't have to reinstall CINELERRA-GG. It is also convenient for the purpose of having the ability to interrupt or to see any possible error messages, if you start the application from a terminal window command line where you will have more control to catch problems. All that said, the system builds can be useful in a university lab setting where there are possibly multiple users, or multiple versions.

There are two notable differences between standard views of CINELERRA-GG and this implementation for the system builds. Both of these can be configured during installation. The differences make it possible to have several different versions installed without having them interfere with each other.

1. application name can be set during a build but defaults to: cin
2. the home configuration directory can also be set and traditionally defaults to: $HOME/.bcast5

#### Footnotes

... systems 3
  Remember that a 32-bit distro does not address more than 4GB of memory, so you may have stability and performance problems with large, high-resolution mediafiles.

Subsections

- The system build
- The single-user build
- 8-bit build for x265 encoding
- Notable Options and Caveats
- Notes about Building from Git in your Customized Environment
- Cloning the Repository for Faster Updates
  - Setting up the initial clone
  - Update an existing repo
  - Useful git commands
- How to Build from a Previous GIT Version
- Debuggable Single User Build
- Unbundled Builds