-1/Aug/97 LilyPond 0.1.0 1
+8/Aug/97 LilyPond 0.1.7 1
Although not strictly necessary, these are recommended to
have.
- +\bo Perl. Most scripts are written in Perl. Most
+ +\bo Perl-5. Most scripts are written in Perl. Most
documentation was created with the perl's Plain
- Old Documentation.
+ Old Documentation. (I use 5.003)
+\bo GNU find
-1/Aug/97 LilyPond 0.1.0 2
+8/Aug/97 LilyPond 0.1.7 2
subdir of tex-prefix)
--enable-mf-dir
- Set then directory mf input is in (idem)
+ Set the directory mf input is in (idem)
[obsolete]
- All options are documented in the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be help
-1/Aug/97 LilyPond 0.1.0 3
+
+8/Aug/97 LilyPond 0.1.7 3
INSTALL(1) LilyPond documentation INSTALL(1)
+ --enable-out-dir
+ Set the directory for machine generated output.
+
+ All options are documented in the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be help
The option -\b-\b-\b--\b-\b-\b-e\be\be\ben\bn\bn\bna\ba\ba\bab\bb\bb\bbl\bl\bl\ble\be\be\be-\b-\b-\b-o\bo\bo\bop\bp\bp\bpt\bt\bt\bti\bi\bi\bim\bm\bm\bmi\bi\bi\bis\bs\bs\bse\be\be\be is recommended for
Real Life usage.
in the subdirectories _\bo_\bu_\bt_\b/ (which contain all
files generated during compilation).
+ B\bB\bB\bBu\bu\bu\bui\bi\bi\bil\bl\bl\bld\bd\bd\bdi\bi\bi\bin\bn\bn\bng\bg\bg\bg f\bf\bf\bfo\bo\bo\bor\br\br\br m\bm\bm\bmu\bu\bu\bul\bl\bl\blt\bt\bt\bti\bi\bi\bip\bp\bp\bpl\bl\bl\ble\be\be\be h\bh\bh\bho\bo\bo\bos\bs\bs\bst\bt\bt\bts\bs\bs\bs
+
+ LilyPond does not follow the GNU standards when it comes
+ to configuring and making Makefiles. In LilyPond, _\bm_\ba_\bk_\be
+ generates _\ba_\bl_\bl output in output directories (called _\bo_\bu_\bt_\b/,
+ by default). You can have multiple compiles from the same
+ source-tree, by overriding the setting for the output
+ directory.
+
+ Example: on my system, I do debugging and lots compiling.
+ For this I use the configuration as follows:
+
+ configure --prefix=~ --enable-debugging --enable-printing --enable-checking
+ make all
+
+ and I want to do profiling. For that I use
+
+ configure --prefix=~ --enable-debugging --disable-printing\
+ --disable-checking --enable-profiling --enable-optimise\
+ --enable-out-dir=out-profile
+
+ make OUTDIR_NAME=out-profile all
+
+ These two commands build two entirely separate versions of
+ LilyPond. In Real Life, you would probably also want to
+ have two different prefixes. On my machine this is no
+ problem; I never do make install. My prefix dirs are
+ linked back to my source directory.
+
I\bI\bI\bIN\bN\bN\bNS\bS\bS\bST\bT\bT\bTA\bA\bA\bAL\bL\bL\bLL\bL\bL\bLI\bI\bI\bIN\bN\bN\bNG\bG\bG\bG
If you have done a successful make, then a simple
Install the musixtex fonts in a directory which TeX and MF
knows (if you are root, look for a directory which
+
+
+
+8/Aug/97 LilyPond 0.1.7 4
+
+
+
+
+
+INSTALL(1) LilyPond documentation INSTALL(1)
+
+
contains the directories with AMS and CM source (*.mf)
files. Create a subdir lilypond or musixtex and copy the
fonts into that). Do not forget to rehash TeX (if
Alpha in dstream.cc. You should turn off this
flag for this file.
+ +\bo Perl5.003 and Perl5.004 use different syntax for
+ pod2html:
+
E\bE\bE\bEX\bX\bX\bXA\bA\bA\bAM\bM\bM\bMP\bP\bP\bPL\bL\bL\bLE\bE\bE\bE
This is what I type in my xterm:
This is what the output looks like over here:
-
-
-
-
-
-
-
-
-
-
-
-1/Aug/97 LilyPond 0.1.0 4
-
-
-
-
-
-INSTALL(1) LilyPond documentation INSTALL(1)
-
-
GNU LilyPond 0.0.78 #4/FlowerLib 1.1.24 #0
Parsing ... [/home/hw/share/lilypond/init//
<..etc..>
create the RPM as a normal user the permissions will not
be set correctly, unfortunately)
-W\bW\bW\bWI\bI\bI\bIN\bN\bN\bND\bD\bD\bDO\bO\bO\bOZ\bZ\bZ\bZE\bE\bE\bE
- Windows NT:
- you need the cygnus windows32 gnu port development stuff;
- have a look at http://www.cygnus.com/gnu-win32.
- to make GNU LilyPond under, brr, aargh, shudder..
+
+
+8/Aug/97 LilyPond 0.1.7 5
+
+
+
+
+
+INSTALL(1) LilyPond documentation INSTALL(1)
+
+
+D\bD\bD\bDE\bE\bE\bEB\bB\bB\bBI\bI\bI\bIA\bA\bA\bAN\bN\bN\bN G\bG\bG\bGN\bN\bN\bNU\bU\bU\bU/\b/\b/\b/L\bL\bL\bLI\bI\bI\bIN\bN\bN\bNU\bU\bU\bUX\bX\bX\bX
+ A Debian package is in the works
+
+W\bW\bW\bWI\bI\bI\bIN\bN\bN\bND\bD\bD\bDO\bO\bO\bOW\bW\bW\bWS\bS\bS\bS N\bN\bN\bNT\bT\bT\bT/\b/\b/\b/9\b9\b9\b95\b5\b5\b5
+ So, you're stuck with Windows, eh? Well, don't worry, you
+ just need (to get) Cygnus' windows32 port of gnu
+ development stuff; have a look at
+ http://www.cygnus.com/gnu-win32.
+
+ To make GNU LilyPond under, brr, aargh, shudder...
windows32, well, simply type:
bash configure
- make windows32
+ make
A\bA\bA\bAU\bU\bU\bUT\bT\bT\bTH\bH\bH\bHO\bO\bO\bOR\bR\bR\bRS\bS\bS\bS
-1/Aug/97 LilyPond 0.1.0 5
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+8/Aug/97 LilyPond 0.1.7 6