![[icon]](../../../../Documentation/pictures/out-www/lelie-icon.png){kind=icon}
GNU LilyPond
Welcome to the home of the GNU Music Typesetter
| What is LilyPond |
|
General information Simple examples Complex examples |
| Download |
|
GNU/Linux binaries Windows Source code |
| Documentation |
|
Tutorial Manual Glossary other ... |
| Support |
|
Mailing lists Search WikiWiki FAQs |
| External sites |
|
lilypond.org/development lilypond.org/stable ftp.lilypond.org Mutopia Other music online |
Node:Other ways to run LilyPond, Next:Integrating text and music, Previous:An orchestral score, Up:Tutorial
Other ways to run LilyPond
Until now, you have been using ly2dvi to invoke LilyPond.
There are three other routes. Firstly, there is a script called
lilypond-book, that allows you to freely mix LilyPond input with
Texinfo or \LaTeX input. For example, this manual was written using
lilypond-book. It is discussed below and in lilypond-book.
Secondly, you can generate PostScript directly. This is useful if you
can not or do not want to run TeX on your system. To obtain direct
PostScript output, invoke LilyPond as follows:
lilypond -f ps test.lyYou have to set some environment variables to view or print this output. More information can be found in Invoking LilyPond. Since the direct Postscript generation has some problems, it is recommended to use
ly2dvi.
Thirdly, if you want to do special things with your output, you can run
invoke LilyPond directly:
lilypond test.lyto produce plain TeX output. Note that LaTeX will not work on the resulting
test.tex. You must run plain TeX on it.
Please send GNU LilyPond questions and comments to lilypond-user@gnu.org.
Please send comments on these web pages to lilypond@packages.debian.org
Copyright (c) 1997--2001 Han-Wen Nienhuys and Jan Nieuwenhuizen.
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.