1 Because installing software in Linux ranges from difficult to
2 impossible we've split up the distributions into three levels of
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>
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>
17 Binary distribution: No thinking involved. These are hosted on <A
18 HREF="http://heroinewarrior.com">Heroinewarrior.com</A><P>
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>
26 The reason for this system is
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>
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>
42 #3 Some of the applications can't be distributed in the same tarball as
43 the libraries because of patents and licenses.<P>
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>
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>
56 Here's the development tree you need to re-enact on your computer to do
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>
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
84 You compile the tree by running <B>configure</B> and <B>make</B> in each of the four
90 export LD_LIBRARY_PATH=.:$LD_LIBRARY_PATH<P>
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>
98 The executables are currently:<P>
101 ./cinelerra/bcast/bcast2000<BR>
102 ./cinelerra/cinelerra/cinelerra<BR>
103 ./xmovie/xmovie/xmovie
106 The plugins are currently:<P>
108 ./cinelerra/plugins<BR>