N\bN\bN\bNA\bA\bA\bAM\bM\bM\bME\bE\bE\bE
- INSTALL - installing LilyPond
+ INSTALL - installing GNU LilyPond
D\bD\bD\bDE\bE\bE\bES\bS\bS\bSC\bC\bC\bCR\bR\bR\bRI\bI\bI\bIP\bP\bP\bPT\bT\bT\bTI\bI\bI\bIO\bO\bO\bON\bN\bN\bN
- This page documents installation and compilation of
+ This page documents installation and compilation of GNU
LilyPond
I\bI\bI\bIM\bM\bM\bMP\bP\bP\bPO\bO\bO\bOR\bR\bR\bRT\bT\bT\bTA\bA\bA\bAN\bN\bN\bNT\bT\bT\bT
P\bP\bP\bPR\bR\bR\bRE\bE\bE\bER\bR\bR\bRE\bE\bE\bEQ\bQ\bQ\bQU\bU\bU\bUI\bI\bI\bIS\bS\bS\bSI\bI\bI\bIT\bT\bT\bTE\bE\bE\bES\bS\bS\bS
For compilation you need.
- +\bo Unix. LilyPond is known to run on Linux, AIX, Digital
- Unix and Solaris
+ +\bo Unix. GNU LilyPond is known to run on Linux, AIX,
+ Digital Unix and Solaris
+
If you have the Cygnus WIN32 port of the GNU utils,
it will even work in Lose NT/95, but don't promise to
support it.
- +\bo GNU C++ v2.7 or better, with libg++ installed. Version
- 2.7.2 or better recommended. I almost positive that
- it will not compile with AT&T CC.
-
- +\bo Bash. Most scripts will continue to work with a stock
- sh, but they will generate (harmless) syntax errors
+ +\bo GNU C++ v2.7 or better, with libg++ installed.
+ Version 2.7.2 or better recommended. I almost
+ positive that it will not compile with AT&T CC.
- +\bo GNU make.
+ +\bo GNU make.
- +\bo Flex (2.5.1 or better).
+ +\bo Flex (2.5.1 or better).
- +\bo Bison.
+ +\bo Bison. (Version 1.25 or better)
R\bR\bR\bRE\bE\bE\bEC\bC\bC\bCO\bO\bO\bOM\bM\bM\bMM\bM\bM\bME\bE\bE\bEN\bN\bN\bND\bD\bD\bDE\bE\bE\bED\bD\bD\bD
- +\bo Perl. Some (mostly unimportant scripts) use Perl for
- trivial operations. The documentation was created
- with the perl's Plain Old Documentation.
+ +\bo Perl. Most scripts are written in Perl. The
+ documentation was created with the perl's Plain Old
+ Documentation.
+\bo (GNU) find
C\bC\bC\bCO\bO\bO\bON\bN\bN\bNF\bF\bF\bFI\bI\bI\bIG\bG\bG\bGU\bU\bU\bUR\bR\bR\bRI\bI\bI\bIN\bN\bN\bNG\bG\bG\bG a\ba\ba\ban\bn\bn\bnd\bd\bd\bd C\bC\bC\bCO\bO\bO\bOM\bM\bM\bMP\bP\bP\bPI\bI\bI\bIL\bL\bL\bLI\bI\bI\bIN\bN\bN\bNG\bG\bG\bG
- to install LilyPond, simply type:
+ to install GNU LilyPond, simply type:
configure
make install
-14/Mar/97 LilyPond 0.0.42 1
+
+
+16/May/97 LilyPond 0.0.64 1
INSTALL(1) LilyPond documentation INSTALL(1)
+ /usr/local/man/man1/mi2mu.1
+ /usr/local/man/man5/mudela.5
/usr/local/man/man1/lilypond.1
+ /usr/local/lib/libflower.{so,a}
/usr/local/bin/lilypond
/usr/local/bin/mi2mu
/usr/local/share/lilypond/*
/usr/lib/texmf/texmf/tex/lilypond/*
+ /usr/lib/texmf/texmf/fonts/source/lilypond/*
The TeX include directory is detected dynamically, but it
- can be adjusted with -\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-t\bt\bt\bte\be\be\bex\bx\bx\bxp\bp\bp\bpr\br\br\bre\be\be\bef\bf\bf\bfi\bi\bi\bix\bx\bx\bx. The above assumes
- that you are root and have the gnu development tools, and
- your make is gnu make. If this is not the case, you can
- adjust your environment variables to your taste:
+ can be adjusted with -\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-t\bt\bt\bte\be\be\bex\bx\bx\bx-\b-\b-\b-p\bp\bp\bpr\br\br\bre\be\be\bef\bf\bf\bfi\bi\bi\bix\bx\bx\bx and -\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-t\bt\bt\bte\be\be\bex\bx\bx\bx-\b-\b-\b-
+ d\bd\bd\bdi\bi\bi\bir\br\br\br. The above assumes that you are root and have the gnu
+ development tools, and your make is gnu make. If this is
+ not the case, you can adjust your environment variables to
+ your taste:
- CXXFLAGS="-I /home/me/my_include -DWEIRD_FOOBAR" configure
+ export CPPFLAGS="-I /home/me/my_include -DWEIRD_FOOBAR"
+ configure
+
+ CPPFLAGS are the preprocessor flags.
the configure script is Cygnus configure, and it will
accept -\b-\b-\b--\b-\b-\b-h\bh\bh\bhe\be\be\bel\bl\bl\blp\bp\bp\bp. If you are not root, you will probably have
configure --prefix=/home/me_myself_and_I/
- Since LilyPond currently is beta, You are advised to also
- use
+ In this case, you will have to set MFINPUTS, and TEINPUTS
+ accordingly.
+
+ If you want to install GNU LilyPond in _\b/_\bu_\bs_\br_\b/_\bl_\bo_\bc_\ba_\bl, and
+ your TeX has no default hooks for local stuff (mine is
+ broken too), you can do:
- --enable-debug
+ configure --prefix=/usr/local --enable-tex-prefix=/usr/lib/texmf
+
+ Since GNU LilyPond currently is beta, you are advised to
+ also use
+
+ --enable-debugging
--enable-checking
other options include:
- --enable-printing
- --enable-optimise
- --enable-profiling
+ --enable-shared
+ Make a shared library (linux, solaris (?) only )
+
+ --enable-printing
+ Enable debugging print routines (lilypond -\b-\b-\b-d\bd\bd\bd option)
+
+ --enable-optimise
+ Set maximum optimisation
+
+
+
- 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
+16/May/97 LilyPond 0.0.64 2
+
+
+
+
+
+INSTALL(1) LilyPond documentation INSTALL(1)
+
+
+ --enable-profiling
+ Compile with support for profiling
+
+ --enable-tex-prefix
+ Set the directory where texmf lives
+
+ --enable-tex-dir
+ Set then directory tex input is in (detected as a
+ subdir of tex-prefix)
+
+ --enable-mf-dir
+ Set then directory tex input is in (idem)
+
+ 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.
If you do
everything will be compiled, but nothing will be
installed. The resulting binaries can be found in the
- subdirectory _\bb_\bi_\bn_\b/.
+ subdirectories _\bo_\bu_\bt_\b/ (which contain all files generated
+ during compilation).
-R\bR\bR\bRU\bU\bU\bUN\bN\bN\bNN\bN\bN\bNI\bI\bI\bIN\bN\bN\bNG\bG\bG\bG
- LilyPond does use a lot of resources. For operation you
- need the following:
+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
- +\bo A fast computer (a full page of music typically takes 1
- minute on my 486/66, using the -\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-c\bc\bc\bch\bh\bh\bhe\be\be\bec\bc\bc\bck\bk\bk\bki\bi\bi\bin\bn\bn\bng\bg\bg\bg
- compile. It's lot slower than most MusiXTeX
- preprocessors)
+ make install
+
+ should do the trick.
- +\bo TeX
+ [todo. Obsolete; fonts are in distribution now.]
+ Install the musixtex fonts in a directory which TeX and MF
+ knows (if you are root, look for a directory which
+ 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
+ applicable)
+ Example: my fonts are in
+ _\b/_\bu_\bs_\br_\b/_\bl_\bo_\bc_\ba_\bl_\b/_\bl_\bi_\bb_\b/_\bt_\be_\bx_\bf_\bo_\bn_\bt_\bs_\b/_\bm_\bu_\bs_\bi_\bx_\bt_\be_\bx_\b/, and I have a symlink
+ pointing to that in
+ _\b/_\bu_\bs_\br_\b/_\bl_\bi_\bb_\b/_\bt_\be_\bx_\bm_\bf_\b/_\bt_\be_\bx_\bm_\bf_\b/_\bf_\bo_\bn_\bt_\bs_\b/_\bs_\bo_\bu_\br_\bc_\be_\b/_\bp_\bu_\bb_\bl_\bi_\bc_\b/
+
+C\bC\bC\bCA\bA\bA\bAV\bV\bV\bVE\bE\bE\bEA\bA\bA\bAT\bT\bT\bTS\bS\bS\bS
+ +\bo The -O2 option to gcc triggers a gcc bug on DEC Alpha
+ in dstream.cc. You should turn off this flag for this
+ file.
+
+R\bR\bR\bRU\bU\bU\bUN\bN\bN\bNN\bN\bN\bNI\bI\bI\bIN\bN\bN\bNG\bG\bG\bG
+ GNU LilyPond does use a lot of resources. For operation
-14/Mar/97 LilyPond 0.0.42 2
+
+16/May/97 LilyPond 0.0.64 3
INSTALL(1) LilyPond documentation INSTALL(1)
- +\bo The MusixTeX fonts. (I use those found in MusixTeX T.59)
+ you need the following:
+
+ +\bo A fast computer (a full page of music typically takes
+ 1 minute on my 486/66, using the -\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-c\bc\bc\bch\bh\bh\bhe\be\be\bec\bc\bc\bck\bk\bk\bki\bi\bi\bin\bn\bn\bng\bg\bg\bg
+ compile. It's lot slower than most MusiXTeX
+ preprocessors)
+
+ +\bo TeX
+
+ +\bo The MusixTeX fonts. (I use those found in MusixTeX
+ T.59). Beware, the clef symbol has changed position
+ in recent versions of MusixTeX)
Please refer to the man page for more information.
R\bR\bR\bRE\bE\bE\bED\bD\bD\bDH\bH\bH\bHA\bA\bA\bAT\bT\bT\bT L\bL\bL\bLI\bI\bI\bIN\bN\bN\bNU\bU\bU\bUX\bX\bX\bX
RedHat Linux users should be able to get a RPM. A spec
- file is in _\bm_\ba_\bk_\be_\b/_\bl_\bi_\bl_\by_\bp_\bo_\bn_\bd_\b._\bs_\bp_\be_\bc.
+ file is in _\bm_\ba_\bk_\be_\b/_\bl_\bi_\bl_\by_\bp_\bo_\bn_\bd_\b._\bs_\bp_\be_\bc. You should be able to
+ create an rpm as a normal user. Be sure you have a
+ ~/.rpmrc, and edit the RPM-dir in _\bV_\ba_\br_\bi_\ba_\bb_\bl_\be_\bs_\b._\bm_\ba_\bk_\be
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 win32 gnu port development stuff; have
a look at http://www.cygnus.com/gnu-win32.
- to make LilyPond under, brr, aargh, well, simply type:
+ to make GNU LilyPond under, brr, aargh, well, simply type:
bash configure
make win32
P\bP\bP\bPL\bL\bL\bLA\bA\bA\bAT\bT\bT\bTF\bF\bF\bFO\bO\bO\bOR\bR\bR\bRM\bM\bM\bMS\bS\bS\bS
- LilyPond (pl 0.0.39) is known to compile on the following
- platforms:
+ GNU LilyPond (pl 0.0.39) is known to compile on the
+ following platforms:
- * linux 2.0.28, g++ 2.7.2[.1]
+ * linux 2.0.x, g++ 2.7.2[.1]
* aix 4.1, g++ 2.7.2
* windows-nt 4.0, cygnus gnu-win32 beta17.1 (~=g++ 2.7.2)
* linux 2.0.28 X to doze, gcc-go32 (~=g++ 2.7.2) [exec. untested]
A\bA\bA\bAU\bU\bU\bUT\bT\bT\bTH\bH\bH\bHO\bO\bO\bOR\bR\bR\bRS\bS\bS\bS
- Han-Wen Nienhuys <hanwen@stack.nl>
+ Han-Wen Nienhuys <hanwen@stack.nl>
- Jan Nieuwenhuizen <jan@digicash.com>
+ Jan Nieuwenhuizen <jan@digicash.com>
Have fun!
-
-
-
-
-
-
-
-
-
-
-
-
-
-14/Mar/97 LilyPond 0.0.42 3
+16/May/97 LilyPond 0.0.64 4
projects / lilypond.git / blobdiff