2 @node Invoking LilyPond, , , Top
3 @chapter Invoking LilyPond
4 @cindex Invoking LilyPond
8 @strong{lilypond} [OPTION]... [MUDELA-FILE]...
15 Output format for sheet music. Choices are tex (for TeX
16 output), ps (for PostScript) and scm (for GUILE)
18 add @file{FILE} to the search path for input files.
20 Disable TeX output. If you have a \midi definition, it will do the
22 @item -M,--dependencies
23 Also output rules to be included in Makefile.
25 Turn debugging info on. GNU LilyPond reads the file @file{.dstreamrc},
26 which lists what functions and classes may produce copious debugging
29 Disallow untrusted @code{\include} directives, backslashes in TeX
30 code and named output.
32 Switch on any experimental features. Not for general public use.
34 Show the warranty with which GNU LilyPond comes. (It comes with
35 @strong{NO WARRANTY}!)
36 @item -o,--output=FILE
37 Set the default output file to @file{FILE}.
39 Show a summary of usage.
41 Set init file to @file{FILE} (default: @file{init.ly}).
42 @item --include, -I=DIRECTORY
43 Add @file{DIRECTORY} to the search path for input files.
44 @item --ignore-version, -V
45 Make the incompatible mudela version warning non-fatal.
50 When invoked with a filename that has no extension, LilyPond will try
51 adding `@file{.ly}' as an extension first, then `@file{.fly}' and
52 finally `@file{.sly}' extension. If the filename ends with
53 `@file{.fly}', LilyPond processes the file as music using
54 `@file{init.fly}'. In this case, LilyPond does something like:
61 1 \input "yourfile.fly"
70 The result of `@file{.sly}' is similar except that a single unjustified
73 If you invoke LilyPond with a file `@file{foo.}@var{ext}' that doesn't
74 have the `@file{.ly}' extension, then LilyPond will look for a file
75 called `@file{init.}@var{ext}' and process this file. The file
76 `@file{init.}@var{ext}' must contain the @code{\maininput} keyword or
77 LilyPond will not read the user specified file.
79 When LilyPond processes @file{filename.ly} it will produce
80 @file{filename.tex} as output. If @file{filename.ly} contains a second
81 @code{\paper} keyword, then LilyPond will produce @file{filename-1.tex}
82 as well. Subsequent @code{\paper} keywords will produce sequentially
83 numbered file names. Several files can be specified; they will each
84 be processed independently.@footnote{Not entirely true: The status of
89 @section Environment variables
93 additional directories for finding lilypond data. The
94 format is like the format of @file{PATH}.
98 selects the language for the warning messages of LilyPond.