From 939b1b23858a06a20e91c3143fa8b5fea34bac63 Mon Sep 17 00:00:00 2001 From: =?utf8?q?=D0=A1=D0=BF=D0=B8=D1=86=D1=8B=D0=BD=20=D0=90=D0=BD=D0=B4?= =?utf8?q?=D1=80=D0=B5=D0=B9?= Date: Mon, 8 Apr 2019 00:48:55 +0300 Subject: [PATCH] Start Instalation part, new font type for listings --- common/packages.tex | 4 +- parts/Instalation.tex | 85 +++++++++++++++++++++---------------------- 2 files changed, 44 insertions(+), 45 deletions(-) diff --git a/common/packages.tex b/common/packages.tex index 7e91d03..01bee8f 100644 --- a/common/packages.tex +++ b/common/packages.tex @@ -8,7 +8,7 @@ \usepackage[bitstream-charter]{mathdesign} % Согласование математических шрифтов \usepackage{ - amsfonts, + %amsfonts, mathtools, mathtext, cite, @@ -54,7 +54,7 @@ \lstset{ % begin settings %language=R, % the language of the code inputencoding=utf8, - basicstyle=\footnotesize, % the size of the fonts that are used for the code + basicstyle=\ttfamily\footnotesize, % the size of the fonts that are used for the code numbers=left, % where to put the line-numbers numberstyle=\tiny\color{black}, % the style that is used for the line-numbers stepnumber=1, % the step between two line-numbers. If it's 1, each line diff --git a/parts/Instalation.tex b/parts/Instalation.tex index 8994974..68b1fac 100644 --- a/parts/Instalation.tex +++ b/parts/Instalation.tex @@ -1,64 +1,63 @@ \chapter{Installation} \label{cha:Instalation} +\section{How to Build Cinelerra-GG from Developer's Git Repository}% +\label{sec:How_to_build} + +These are generic build instructions for building Cinelerra-GG Infinity. +Known to work on ubuntu, mint, suse/leap, fedora, debian, centos, arch, and slackware. +It has not been tested on every single possible distro yet so you might expect to have to make some minor changes. +Patches have been created to build on FreeBSD through the work of another programmer and a Gentoo version is being maintained elsewhere by another programmer. + +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. -This manual covers features or areas of Cinelerra that are different or new in the Cinelerra-GG Infinity -version. Many of the new features were created by a lot of different people to include the original -author and were merged in from various sources and each person is to be commended for their efforts. -The content of this manual also came from various people/places/email and thanks to all. -The standard Cinelerra Manual covers “The Secrets of Cinelerra” and can be found at:\par \url{ -https://cinelerra-cv.org/docs/cinelerra_cv_manual_en.html +https://cinelerra-gg.org/download/ } -\section{How to Build Cinelerra-GG Infinity from Developer's Git Repository}% -\label{sec:} - -These are generic build instructions for building Cinelerra-GG Infinity. Known to work on ubuntu, -mint, suse, fedora, debian, centos, arch, and 32-bit slackware. It has not been tested on every single -possible distro yet so you might expect to have to make some minor changes. It has failed miserably -on FreeBSD. At least once, a Gentoo version was successfully created. - -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 link below. See Section 1.2. - -\url{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. Also, if you install a new -Operating System version and if you have Cinelerra on separate disk space that is preserved, you won't -have to reinstall Cinelerra. In addition for purposes of having the ability to interrupt or to see any -possible error messages, if you start the application from a terminal window command line you will -have more control to catch problems. 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 and this implementation for -the system builds. Both of these can be configured during installation. These differences make it -possible to have several different versions installed without having them “walk” on each other.ault system-build an + +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. +Also, if you install a new Operating System version and if you have Cinelerra on separate disk space that is preserved, you won't have to reinstall Cinelerra. +In addition for purposes of having the ability to interrupt or to see any possible error messages, if you start the application from a terminal window command line you will have more control to catch problems. +However, 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 and this implementation for the system builds. +Both of these can be configured during installation. +These differences make it possible to have several different versions installed without having them “walk” on each other. + + + + + + + + + +%===== \begin{enumerate} \item application name can be set during installation and defaults to: “\texttt{cin}” - \item - the home configuration directory can also be set and defaults to:\\ “\texttt{\$HOME/.bcast5}” - - + \item + the home configuration directory can also be set and defaults to:\\ “\texttt{\$HOME/.bcast5}” \end{enumerate} + \paragraph{To do a system build,} you should read the \texttt{README} that is at the top level after you get the source. \begin{enumerate} \item - You need at least 2.5GB of disk storage to operate a build. Need to have “\texttt{git}” installed. + You need at least 2.5GB of disk storage to operate a build + you need to have “\texttt{git}” installed. \item Obviously in order to install into the system, you must run as root. - \item The "\texttt{git}" step has to download a bunch of stuff (approx 100MB) so allow time. + \item The "\texttt{git}" step has to download many files (approx 100MB) so allow time. \item Run the following commands (this takes awhile): + \begin{lstlisting}[language=bash] -cd // -# this is where you need the 2.5GB of disk space +cd // # this is where you need the 2.5GB of disk space git clone --depth 1 "git.cinelerra-gg.org/goodguy/cinelerra.git" cinelerra5 cd cinelerra5/cinelerra-5.1 # toplevel directory \end{lstlisting} -- 2.26.2