7 Some questions that have been answered before.
15 to make a few chords, but why do I have to type
18 < { a() e } { c () g } >
24 to generate slurs between the chords?
32 < { a } { c } > < { e } { g } >
34 Slurs have to be confined to `voices', and the a and the e are in
35 different {} blocks, so they are in different voices. You should view
36 the desired construct as a "generalised chord" (two voices stacked
37 vertically). It might help you visualise this by using the following
45 Q: Why are [] around the notes, and () inbetween?
47 A: [] designate beams, a note can only be in one beam at the same
48 time. () is a slur, which connects notes. You need to be able to
53 Q: Why shouldn't I put all commands (\clef, \meter) inside the music?
55 A: You should do what you like, but at some time we will enable
56 quoting of music ("Stichnoten"). Besides if you are going to type an
57 orchestral score, then you'd probably want to enter most of the meter,
58 repeat commands only once.
66 Q: Could you implement feature XXXX? It is really easy, just extend
67 the syntax to allow YYYY!
69 A: If it is reasonable, I'll add XXXX to the TODO list. In general
70 finding a cute syntax (such as YYYY) isn't very hard. The complicated
71 issue how to adapt the internals to do XXXX. The parser is really a
72 simple front end to the complicated internals.
74 Q: Why do I need g++ >= 2.7?
76 A: By using g++ LilyPond is portable to all platforms which support
77 g++ (there are quite a few). Not having to support other compilers
78 saves us a I<lot> of trouble. LilyPond and FlowerLib use:
86 64 bit integral type long long
92 operator <?, operator >?
98 class Rational (libg++)
109 can't load library 'libflower.so'
111 A: You are using the dynamically compiled Flower library. Please set
112 LD_LIBRARY_PATH to a directory containing F<libflower.so>
116 Q: I want a DOS/NT/W95 port.
118 A.0: Reconsider. Try Linux. It's fun!
120 A.1: Currently (patchlevel 27), LilyPond (and flowerLib) compiles, links
121 and runs on windhoos-nt, using the cygnus gnu port (release b17.1).
122 I (JCN) only had to make a minor workaround for missing library calls.
123 Have a look at http://www.cygnus.com/gnu-win32. To make LilyPond type
124 C<make $OSTYPE>. (I am not promising to maintain this platform, it is just
125 that when having to use doze, i-m sometimes too lazy to reboot.)
127 A.2: I haven't had time to find a GCC crosscompiler (I<with> g++ and
128 libg++, mind you) to DOS/win (in rpm, please :).
131 Q: I-m dozed enough to run the (sometimes bit stale) .exe-s you distribute.
132 Why do i need cygwin.dll?
134 A: It-s all in this cut-n-paste:
136 Minimalist GNU-Win32 Readme
139 Colin Peters <colin@bird.fu.is.saga-u.ac.jp>
143 0.3 Fixes and Improvements
146 In the "coming soon" category I have a version of the GNU Standard C++
147 library ported to Mingw32. This means you can use iostreams, complex
148 numbers and all those neat STL (Standard Template Library) things
149 without needing the Cygwin DLL. I hope to put this port up for
150 downloading soon (along with the source of course).
156 To add C++ Support to the above the following extra files are required:
158 In C:\cygnus\H-i386-cygwin32\lib\gcc-lib\i386-cygwin32\cygnus-2.7.2-
162 Note that this does not include support for the standard C++ libraries
163 (only the C run time libraries) or for iostreams. That support is still
164 only available with the Cygwin32 API.