hvirtual/doc/doc_2002.html

   1 Compiling the backups<P>
   2
   3
   4
   5
   6
   7
   8
   9
  10 <P>Be aware the backups come with<P>
  11
  12 NO WARRANTY<P>
  13
  14 NO SUPPORT<P>
  15
  16 NO GUARANTEE OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE<P>
  17 <P>
  18
  19 Because installing software in Linux ranges from difficult to
  20 impossible you should consider first why you want to do this to
  21 yourself and second how much better your life will be if you
  22 succeed.<P>
  23
  24
  25 The reason for this system of backups instead of more traditional CVS,
  26 snapshot, IRC room, or rejected slashdot submission is
  27
  28 <BLOCKQUOTE>
  29
  30 #1 The libraries and tools are very esoteric and useless to most
  31 consumers.  They are no substitute for bona-fide home entertainment
  32 systems.<P>
  33
  34 #2 The libraries and tools are shared across many applications.  Many
  35 esoteric and useless applications, that is.  Changes to the libraries
  36 must be propagated to the applications without involving a hairball of
  37 standard lib directories or cp -a'ing the libraries after every
  38 change.<P>
  39
  40 #3 People hate software that costs money.  People hate free software
  41 that doesn't have support even more.  Only people who like compiling
  42 software instead of retaliating for lack of support are going to bother
  43 compiling backups.<P>
  44
  45 </BLOCKQUOTE>
  46
  47 Enter the <I>symbolic linking</I> paradigm.  The biggest reason users
  48 can't understand our development tree structure is that Microsoft is
  49 king and symbolic linking doesn't exist in Windows.<P>
  50
  51 When you symbolically link something, it appears in the directory just
  52 like the original file would, except it's really an illusion.  Changes
  53 made to the original file appear in every symbolic link to it, as if
  54 you changed many copies of the file.<P>
  55
  56 Here's the development tree you need to re-enact on your computer to do
  57 development:<P>
  58
  59 <PRE>
  60 ./
  61 ./libmpeg3
  62 ./quicktime
  63 ./cinelerra
  64 ./xmovie
  65 </PRE>
  66
  67 The first step in constructing this development tree is downloading the
  68 backups.  The latest version of the following files must be downloaded
  69 and decompressed into ./:<P>
  70
  71 <B>
  72 <PRE>
  73 cinelerra.*.tar.bz2
  74 libmpeg3.*.tar.bz2
  75 quicktime.*.tar.bz2
  76 xmovie.*.tar.bz2
  77 </PRE>
  78 </B>
  79
  80 <P>
  81
  82 The CFLAGS environment variable must be set with optimization flags.
  83 The best optimization flags are<P>
  84
  85 <B>-O3 -march=i686 -fmessage-length=0
  86 -funroll-all-loops -fomit-frame-pointer -malign-loops=2 -malign-jumps=2
  87 -malign-functions=2</B><P>
  88
  89 You compile Cinelerra by running <B>make</B> and <B>make install</B> in
  90 <B>./cinelerra</B>.<P>
  91
  92 You compile XMovie by running <B>make</B> and <B>make install</B> in
  93 <B>./xmovie</B>.<P>
  94
  95 The executables are currently:<P>
  96
  97 <PRE>
  98 /usr/bin/cinelerra<BR>
  99 /usr/bin/xmovie
 100 </PRE>
 101
 102 The plugins are currently:<P>
 103 <PRE>
 104 /usr/lib/cinelerra/*<BR>
 105 </PRE>