X-Git-Url: https://git.cinelerra-gg.org/git/?p=goodguy%2Fcin-manual-latex.git;a=blobdiff_plain;f=parts%2FInstalation.tex;h=0059bc7e565e6c8874d3a01d33d7867a0b0200eb;hp=d84630dae5fd139b2b25245acaa06346af798ee1;hb=171dd1055e0a148862f4b082e277c9971621b244;hpb=38f03d5451cd9b5537ced6c0a5a007df55ad62ef

diff --git a/parts/Instalation.tex b/parts/Instalation.tex
index d84630d..0059bc7 100644
--- a/parts/Instalation.tex
+++ b/parts/Instalation.tex
@@ -21,7 +21,7 @@ The majority of the files are installed in the standard system paths, but some c
 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.  
+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.
@@ -48,6 +48,7 @@ These differences make it possible to have several different versions installed
 
 \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.5\,GB of disk storage to operate a build + you need to have “\texttt{git}” installed.
@@ -131,19 +132,19 @@ These procedures and the Cinelerra-GG Infinity software have all been run as “
 To see the full list of features use:	 
 
 \begin{lstlisting}[language=bash]
-$ ./configure –help
+$ ./configure -help
 \end{lstlisting}
 The default build is a system build which uses:    
 
 \begin{lstlisting}[language=bash]
-$ ./configure –without-single-user
+$ ./configure -without-single-user
 \end{lstlisting}
 
 In the single-user build, the target directory is always “cin”.  
 Because this is also the developer build, constant names are used throughout.  
 However, you can rename files after the install is complete.
 
-f your distro/operating system has issues with the default install to \texttt{/usr/local}, you might have to change the location to /usr for a system build.  Then you will have to use:
+If your operating system has issues with the default install to \texttt{/usr/local}, you might have to change the location to \texttt{/usr} for a system build.  Then you will have to use:
 \begin{lstlisting}[language=bash]
 $ ./configure --prefix=/usr
 \end{lstlisting}
@@ -158,11 +159,11 @@ The application name can be set during installation, but defaults to cin so that
 $ ./configure --with-exec-name=cinelerra
 \end{lstlisting}
 
-The home configuration directory can also be set, but defaults to \texttt{\$\$HOME/.bcast5}.  
+The home configuration directory can also be set, but default location is \texttt{\$HOME/.bcast5}.  
 For example:
 
 \begin{lstlisting}[language=bash]
-$ ./configure –with-config-dir=/myusername/.bcast5
+$ ./configure -with-config-dir=/myusername/.bcast5
 \end{lstlisting}
 
 NOTE:  when you specify parameters to the configure program, it will create a make file as a consequence.  
@@ -236,15 +237,15 @@ The "yes" means force build and “auto” means probe and use the system versio
 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 \texttt{configure.ac} script.  
 There may be several libraries which need special treatment.
 
-An example of a problem you might encounter with your customized installation is with “\texttt{a52dec}” which has probes \texttt{(CHECK\_LIB/CHECK\_HEADER)} in \texttt{configure.ac}, but \texttt{djbfft} does not.  
+An example of a problem you might encounter with your customized installation is with “\texttt{a52dec}” which has probes line \texttt{(CHECK\_LIB/CHECK\_HEADER)} in \texttt{configure.ac}, but \texttt{djbfft} does not.  
 In this case, \texttt{djbfft} is only built because \texttt{a52dec} is built, so if your system has \texttt{a52dec}, set \texttt{a52dec} to auto and see if that problem is solved by retrying the build with:  
 \begin{lstlisting}[language=bash]
-$ ./confgure --with-single-user –enable-a52dec=auto .
+$ ./confgure --with-single-user -enable-a52dec=auto .
 \end{lstlisting}
 
 With persistence, you can get results, but it may take several tries to stabilize the build.  
 If you need help, email the "\texttt{log}" and "\texttt{config.log}", which is usually sufficient to determine why a build failed.
-\vspace{5ex}
+%\vspace{5ex}
 
 If you have already installed the \texttt{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.
 
@@ -375,7 +376,7 @@ $ ./bld.sh
 Then, to run as a developer in the debugger:
 
 \begin{lstlisting}[language=bash]
-$ CFLAGS=”-O2 -ggdb” make -j8 rebuild_all
+$ CFLAGS="-O2 -ggdb" make -j8 rebuild_all
 $ cd cinelerra
 $ gdb ./ci
 \end{lstlisting}
@@ -390,7 +391,7 @@ The names of the build scripts are:  arch.bld ,  bsd.bld , deb.bld , and rpm.bld
 These scripts are in the “blds” subdirectory.  
 The bsd.bld should be used with the bsd.patch file in that same directory.
 
-The reason that Cin Infinity traditionally uses thirdparty builds (bundled builds) is because there are a lot of different distros with varying levels of ffmpeg and other needed thirdparty libraries.  
+The reason that Cin Infinity traditionally uses thirdparty builds (bundled builds)\todo{hanging line} is because there are a lot of different distros with varying levels of ffmpeg and other needed thirdparty libraries.  
 However, some users prefer using their current system baseline without another/different copy of ffmpeg.  
 With different levels of the user’s libraries, uncertainty, potential instability, and unknown issues may come up while running Cinelerra and this will make it, for all practical purposes, impossible to diagnose and debug problems or crashes.  
 There may be no help in these cases.  You are encouraged to report any errors which potentially originate from Cin Infinity, but if the data indicates alternate library sources, please report the problems to the appropriate maintainers.
@@ -446,12 +447,12 @@ If repository problems, usually you can manually do an install by using:
   wget https://cinelerra-gg.org/download/pkgs/{substitute_name}/cin_5.1.<sub_name>.deb
   and install it manually, for example: dpkg -i cin_5.1.{substitute_filename}.deb
 
-# GENTOO – courtesy Dominque Michel
+# GENTOO - courtesy Dominque Michel
 # There is an ebuild package at this time as of 01/03/2019 at:
 #    https://svnweb.tuxfamily.org/listing.php?repname=proaudio%2Fproaudio&path=
 #    %2Ftrunk%2Foverlays%2Fproaudio%2Fmedia-video%2Fcinelerra%2F&#ab000caf7024d83112f42a7e8285f2f29
 
-# FREEBSD – courtesy Yuri
+# FREEBSD - courtesy Yuri
 # There is a port available at: https://www.freshports.org/multimedia/cinelerra-gg/
 # To use this port: cd /usr/ports/multimedia/cinelerra-gg && make install clean
 #   and then install this precompiled package via: pkg install cinelerra-gg