@section Downloading
-Even numbered minor versions are `stable' (2.2, 2.4 etc), while odd
-version are development releases (2.3, 2.5, etc). Building LilyPond
+Even numbered minor versions are `stable' (2.6, 2.8, etc), while odd
+version are development releases (2.7, 2.9, etc). Building LilyPond
is an involved process. If possible
@uref{http://lilypond.org/download,download a precompiled binary}
for your platform.
@subsection Precompiled binary packages
-Check out @uref{http://lilypond.org/download} for up to date information on
-binary packages for your platform.
+Check out @uref{http://lilypond.org/web/install/} for up to date
+information on binary packages for your platform.
@section Requirements
@itemize
-@item @uref{http://fontforge.sf.net/,FontForge} 20041211 or newer.
+@item @uref{http://fontforge.sf.net/,FontForge} 20060125 or newer.
-@item @uref{http://www.xs4all.nl/~hanwen/mftrace/,mftrace} (1.1.0 or
+@item New Century Schoolbook fonts, as PFB files. These are shipped
+with X11 and Ghostscript, and are named @file{c059033l.pfb}
+@file{c059036l.pfb}, @file{c059013l.pfb} and @file{c059016l.pfb}
+
+@item @uref{http://www.xs4all.nl/~hanwen/mftrace/,mftrace} (1.1.19 or
newer),
You will need to install some additional packages to get mftrace to
work.
@item @uref{http://www.gnu.org/software/guile/guile.html,GUILE}
-(version 1.6.5 or newer). If you are installing binary packages, you
+(version 1.6.7 or newer). If you are installing binary packages, you
may need to install guile-devel or guile-dev or libguile-dev too.
-@item @TeX{}.
+@item @uref{ftp://ftp.gnu.org/gnu/texinfo/,Texinfo} (version 4.8 or newer).
-@TeX{} is used as an optional output backend.
+@item
+ @uref{http://gcc.gnu.org/, The GNU c++ compiler} (version 4.x or
+newer).
-Also, @TeX{}'s libkpathsea is used to find the fonts (@file{.mf},
-@file{.afm}, @file{.tfm}). Make sure you have tetex 1.0 or newer
-(1.0.6 is known to work). If you are installing binary packages, you
-may need to install tetex-devel, tetex-dev or libkpathsea-dev too.
+@item @uref{http://www.python.org,Python} (version 2.3 or newer)
+@item @uref{ftp://ftp.gnu.org/gnu/make/,GNU Make} (version 3.78 or newer).
-@item @uref{ftp://ftp.gnu.org/gnu/texinfo/,Texinfo} (version 4.7 or newer).
+@item @uref{http://www.gnu.org/software/gettext/gettext.html,gettext}.
-@item
- @uref{http://gcc.gnu.org/, The GNU c++ compiler} (version 3.1 or
-newer). EGCS and 2.x are known to cause crashes.
-@item @uref{http://www.python.org,Python} (version 2.1 or newer).
+@item @uref{http://www.gnu.org/software/flex/,Flex}
-@item @uref{ftp://ftp.gnu.org/gnu/make/,GNU Make} (version 3.78 or newer).
+@item @uref{http://www.perl.org/,Perl}
-@item @uref{http://www.gnu.org/software/gettext/gettext.html,gettext}.
+@item @uref{http://www.gnu.org/software/flex/,GNU Bison}
@item All packages required for running, including development packages with
header files and libraries.
@itemize @bullet
@item @uref{http://www.freetype.org/,Freetype} (version 2).
+@item @uref{http://www.freetype.org/,FontConfig} (version 2.2).
@item @uref{http://www.pango.org/,Pango} (version 1.6 or newer).
@item @uref{http://www.gnu.org/software/guile/guile.html,GUILE}
(version 1.6.5 or newer).
@item @uref{http://www.python.org,Python} (version 2.1 or newer).
@item @uref{http://www.ghostscript.com,Ghostscript} (version 8.15 or
-newer).
+newer. 8.50 recommended)
@end itemize
@subsection Building documentation
Building the website requires some additional tools and packages
@itemize @bullet
-@item @uref{http://lilypond.org/download/fonts,ec-fonts-mftraced}
@item The @uref{http://netpbm.sourceforge.net/,netpbm utilities}
@item ImageMagick
@item International fonts (see input/regression/utf-8.ly for hints
about which font packages are necessary for your platform)
+@item Ghostscript, 8.50 with the patch from
+@uref{http://bugs.ghostscript.com/show_bug.cgi?id=688154}
+and the patch from
+@uref{http://bugs.ghostscript.com/show_bug.cgi?id=688017}.
@end itemize
The HTML files can be installed into the standard documentation path
@end example
@end quotation
-@ignore
-In this case, you have to insert the contents of
-@code{buildscripts/out/lilypond-login} or
-@code{buildscripts/out/lilypond-profile} into your start up scripts by
-hand.
-@end ignore
-
@subsection Configuring for multiple platforms
@section Vim mode
A Vim mode for entering music and running LilyPond is contained in the
-source archive in @code{$VIM} directory. For version 6.2 and newer,
-Vim-mode works directly after installing LilyPond. Otherwise,
-complete the following two steps.
+source archive in @code{$VIM} directory.
-For earlier versions (and if @code{$VIM} environment variable does not
-fall-back to @file{/usr/local/share/vim}, see @code{:version} in vim),
-the LilyPond file type is detected if your file @file{~/.vim/filetype.vim} @c
+The LilyPond file type is detected if the file @file{~/.vim/filetype.vim} @c
has the following content
@quotation
@example
augroup END
@end example
@end quotation
-If Vim has been (pre-)installed to @file{/usr/...} (or any other place)
-instead of @file{/usr/local/...}, then @file{/usr/local/share/vim} may not
-be specified in your @code{$VIMRUNTIME} environment variable and you have to
-include this path explicitly by appending the following line to your
+
+Please include this path by appending the following line to your
@file{~/.vimrc}
+
@quotation
@example
-set runtimepath+=/usr/local/share/vim/
+set runtimepath+=/usr/local/share/lilypond/$@{LILYPOND_VERSION@}/vim/
@end example
@end quotation
+@noindent
+where $@{LILYPOND_VERISON@} is your lilypond version. If Lilypond was not
+installed in @file{/usr/local/}, then change this path accordingly.
+
+
@section Problems
For help and questions use @email{lilypond-user@@gnu.org}. Send bug
@end example
@end quotation
-@subsection Linking to kpathsea
-
-If kpathsea and the corresponding header files are installed in some
-directory where GCC does not search by default, for example in
-@file{/usr/local/lib/} and @file{/usr/local/include/} respectively,
-you have to explicitly tell configure where to find it. To do this
-
-@itemize
-@item @code{rm config.cache}
-@item @code{export LDFLAGS=-L/usr/share/texmf/lib}
-@item @code{export CPPFLAGS=-I/usr/share/texmf/include}
-@item @code{./configure}
-@end itemize
-Once configure has found them, the paths are stored in
-@file{config.make} and will be used even if you don't have the
-environment variables set during make.
@unnumberedsubsec Gcc-3.0.4
projects / lilypond.git / blobdiff