doc/doc_2000.html

   1 Because installing software in Linux ranges from difficult to
   2 impossible we've split up the distributions into three levels of
   3 difficulty:<P>
   4
   5 <BLOCKQUOTE>
   6
   7 Development trees:  virtually impossible to compile without software
   8 development experience but allow you to submit changes to the source
   9 code.  These are hosted in <A
  10 HREF="http://heroines.sourceforge.net">heroines.sourceforget.net</A>.<P>
  11
  12 Source code distribution:  very hard to compile from scratch but doable
  13 in a single month.  It's very hard to submit changes to the source
  14 code.  These are hosted in <A
  15 HREF="http://heroinewarrior.com">Heroinewarrior.com</A><P>
  16
  17 Binary distribution:  No thinking involved.  These are hosted on <A
  18 HREF="http://heroinewarrior.com">Heroinewarrior.com</A><P>
  19 </BLOCKQUOTE>
  20
  21 The current state of heroines.sourceforge.net is the raw development
  22 trees.  There are scripts in the development trees which automatically
  23 package it into source code and binary distributions which users can
  24 download and install in less than a month.<P>
  25
  26 The reason for this system is
  27
  28 <BLOCKQUOTE>
  29
  30 #1 The libraries and tools are very esoteric and rapidly evolving.  It
  31 would be impossible for users to manually search and install every
  32 library and tool required to install Broadcast 2000.  Instead, as many
  33 libraries and tools as possible are statically built into the
  34 executables, isolating the user from the bird's nest of standard lib
  35 directories and Google searches.<P>
  36
  37 #2 The libraries and tools are shared across many applications.
  38 Changes to the libraries must be propagated to the applications without
  39 involving the hairball of standard lib directories and without cp
  40 -rd'ing the libraries after every change.<P>
  41
  42 #3 Some of the applications can't be distributed in the same tarball as
  43 the libraries because of patents and licenses.<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 Windows is king
  49 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 directories from <B>ftp://heroines.sourceforge.net/pub/heroines/</B>.
  69 The following files must be downloaded and decompressed:<P>
  70
  71 <B>
  72 <PRE>
  73 cinelerra.tar.bz2
  74 libmpeg3.tar.gz
  75 quicktime.tar.gz
  76 xmovie.tar.gz
  77 </PRE>
  78 </B>
  79
  80 Don't expect to compile anything useful out of this.  When you compile
  81 this tree you get executables which run where they are for testing
  82 purposes.<P>
  83
  84 You compile the tree by running <B>configure</B> and <B>make</B> in each of the four
  85 directories.<P>
  86
  87 Enter <P>
  88
  89 <PRE>
  90 export LD_LIBRARY_PATH=.:$LD_LIBRARY_PATH<P>
  91 </PRE>
  92
  93
  94 into your
  95 .bashrc, .bash_login, .bash_profile files and log into another Xterm.  Now you can cd
  96 into a directory and run an executable.<P>
  97
  98 The executables are currently:<P>
  99
 100 <PRE>
 101 ./cinelerra/bcast/bcast2000<BR>
 102 ./cinelerra/cinelerra/cinelerra<BR>
 103 ./xmovie/xmovie/xmovie
 104 </PRE>
 105
 106 The plugins are currently:<P>
 107 <PRE>
 108 ./cinelerra/plugins<BR>
 109 </PRE>