1 @section Obtaining LilyPond
3 You can get the latest version of LilyPond at
4 @uref{ftp://ftp.lilypond.org/pub/LilyPond/,
5 ftp://ftp.lilypond.org/pub/LilyPond/}.
7 @section Windows build requirements
8 You need the following packages to compile Lilypond on Windows.
11 @item The GNU + Cygnus tools, 1.1.7 or newer.
12 Check out the @uref{http://sources.redhat.com/cygwin,Cygwin webpage}.
13 You can get the latest version of the GNU + Cygnus tools from cygnus
14 @uref{http://sources.redhat.com/cygwin/mirrors.html,mirror site}.
15 Install everything, including tetex.
16 @item GUILE 1.4, or newer.
17 Check out the @uref{http://www.gnu.org/software/guile.html,GUILE
18 webpage}. You may need the patch @file{guile-1.4-gnu-windows.patch}
19 included in LilyPond's source distribution.
22 @subsection Cross compiling
24 These binaries are cross compiled for Windows on a GNU/Linux box. You
25 may want to check out the
26 @uref{http://www.lilypond.org/gnu-windows/cross.tar.gz,cross compilation
29 @subsection Compiling on Windows
31 Compiling on Windows should be possible, but how should we now? If you
32 have any experiences you want to share, please do so at
33 @uref{http://lilypond.org/wiki?CompilingOnWindows,Compiling on Windows}.
34 Or write to one of the mailing lists.
36 @section Windows installation specifics
38 Installing LilyPond on Windows is similar to a unix installation, but
39 needs a number of extra tricks. All code for these tricks can be found
40 in the source package directory @file{Documentation/windows}.
43 @item @var{guile-1.4-gnu-windows.patch}
44 You may (Cygwin gets better every day) need this patch to compile GUILE.
45 @item @var{cygwin-installer.patch}
46 Apply this patch to the @file{cinstall} directory of
47 @file{winsup-src/cinstall}, to get the LilyPond installer.
49 Compiling @file{setup.exe} has been complicated a bit with the
50 introduction of the non-feature bzip2. Here's how I did it:
53 tar xjf cygwin-src-20010531.tar.bz2
54 tar xjf winsup-src-20010531.tar.bz2
55 tar xzf mingw-20010424-1.tar.gz
57 patch < ../../cygwin-installer.patch
58 cp /home/cygwin/cygwin-1.3.2/usr/lib/mingw/crt2.o .
60 MINGW32=yes CFLAGS='-mno-cygwin' ./configure
63 make w32api_lib=/home/cygwin/cygwin-1.3.2/usr/lib/w32api \
64 CXX='g++ -L/home/cygwin/cygwin-1.3.2/usr/lib/mingw'
67 @item @var{--prefix=/usr/lilypond-x.y.x}
68 The standard binary installation installs LilyPond into its own prefix.
69 We think it's silly, but do this is on special request of Windows users.
70 @item @file{fix-suffixes.sh}
71 Add @file{.exe} to binary executables, add @file{.py} to Python scripts.
72 @item @file{python-wrapper.sh}
73 All python scripts get a wrapper script to make direct invocation easier
74 and to change file paths to DOS style, which is needed by non-Cygwin
75 Python, that's currently used.
76 @item @file{latex-wrapper.sh}
77 TeX and LaTeX get a wrapper script that changes the TEX path variables
78 to DOS style, which is needed by non-Cygwin TeX, that's currently used.
79 @item @file{/etc/postinstall/}
80 A number of post installation scripts try to set registry entries and
81 symlinks that are needed for the additional windows packages.
82 @item @file{/etc/profile.d/}
83 A number of login profile scripts set environment vars, every time you
84 start the LilyPond/Cygwin shell (or Bash, for that matter).
87 These scripts and tricks are known to work in some cases, but are
88 woefully incomplete. If you find a bug, please send us your fix.
90 Windows users have indicated that a DOS style login (as supposed to the
91 LilyPond/Cygwin shell), would be useful. We don't enjoy DOS scripting,
92 and think users should try the bash shell, which is better suited for
93 typing in commands. However, if you have written useful DOS login
94 scripts, please send us your code.