On 11/6/99, 11:34:37 AM, "Shamus" <[EMAIL PROTECTED]>
wrote regarding Compiling Win32 version:
> Ok, I figured since the last version of lily for Win32 is
> *still* 1.2.0
There is no reason to yell. I just simply bit off more
than I could chew.
> What happened to it? And, more to the point, just how do you go
> about compiling for Win32?
Enclosed is the text version of documentation you are speaking of.
I would be pleased to have someone else help in this effort. The
last time I compiled was 1.2.14, so I think there are some
significant changes like upgrading guile.
--
Jeffrey B. Reed
mailto:[EMAIL PROTECTED]
LilyPond on W32
Jan Nieuwenhuizen and Jeffrey Reed
Contents
1: DISCLAIMER
1.1: INSTALL
1.2: BUILDING LILYPOND
1.3: GOOD NEWS
1.4: UNPACKING
1.5: ABOUT UNIX
2: LILYPOND Windows-NT Support -- by Jeffrey Reed
2.1: Building lilypond on Windows-NT
2.1.1: Cygnus Development Kit
2.1.2: Ecgs Compiler, assembler, and linker
2.1.3: GNU's Internationalization Package
2.1.4: GNU's roff package
2.1.5: Python Programing Language
2.1.6: Perl Programing Language
2.1.7: Yodl Document Language
2.1.8: guile
2.1.9: LilyPond
2.2: Maintaining lilypond on Windows-NT
2.3: Running lilypond on Windows-NT
3: RUNNING LILYPOND -- by Dominique Cretel
4: PROBLEMS AND ANWSWERS
4.1: CONFIGURE AND INSTALL
4.2: DRIVE D:
4.3: INSTALLING TOOLS
4.4: VIRTUAL MEMORY
No, there's no reason to be concered, Lily should work in
Windows-NT(/95/98?) too. The setup may not be easy or
smooth. This document will help you getting started.
1: DISCLAIMER
If you have the Cygnus gnu-windows32 port of the GNU utils,
LilyPond will work in Windows-NT (/95/98?).
We still recommend you use Unix. In particular, use
GNU/Linux: We've been there, and we've seen it happen sev-
eral times. It is much easier and quicker to install RedHat
Linux and LilyPond than to obtain, compile and install all
the necessary tools to compile and run LilyPond on Windows.
``Ok, thanks for the suggestions. I can't run Linux or I
don't want to run Unix. What can I expect?''
o LilyPond development is moving quite fast, and all
developers use Unix. Newly added features may require
some attention to get them to work.
o LilyPond depends on a number of other packages that
usually are available on Unix boxes, but are not
installed by default on Windows.
1.1: INSTALL
Like Yodl, LilyPond will now install/extract in a unix-like
tree:
usr/[local/]bin/
usr/[local/]share/lilypond/*
etc.
Both Yodl and Lily run in a the unix-like Cygnus gnu-windows
environment; hopefully Cygnus will adopt the /usr/[local/]
tree too.
If you really don't want usr/ in your root directory, but
rather scatter your programs and packages all over your
harddisk, do something like:
md lilypond
cd lilypond
unzip ../lilypond-0.1.77.exe.zip
and add lilypond/usr/bin to your PATH and lily-
pond/usr/share/lilypond to your LILYINCLUDE.
1.2: BUILDING LILYPOND
If you've received a binary release of LilyPond (.exe.zip),
you may skip the following sections.
1.3: GOOD NEWS
It can be done! Occasionally, the Cygnus b19.1 cross com-
piler and utilities under GNU/Linux are used to make the
binary .exe.zip releases (some makefile hacking was needed
to build this stuff). Jeffrey Reed tries to keep-up with
LilyPond development, and is doing quite well. His latest
release is available on
http://home.austin.rr.com/jbr/jeff/lilypond/.
1.4: UNPACKING
I have heard of such tools that think they're probably much
smarter than the packager and thus decide for themselves
that they don't need to unpack certain files (e.g., empty
directories such as bin/out).
To unpack the lilypond sources, you should do something
like:
tar zxf releases/lilypond-x.y.z.tar.gz
1.5: ABOUT UNIX
If you're familiar with the GNU/Cygnus development package,
you may skip this.
Don't forget to set
/start/settings/control-panel/system/environment/system-variables:
GCC_EXEC_PREFIX=/Cygnus/b19/H-i386-cygwin32/lib/gcc-lib/
MAKE_MODE=UNIX
You want to run bash, while building Lily:
c:\bash
bash-2.01$
The install instructions mention something like:
configure
make
make install
Now for a small UNIX lesson: The current working directory
(cwd) is by default not in your PATH, like it is under DOS
(for security reasons). Check this by looking at the output
of:
echo $PATH
The cwd looks like '::' or ':.'. If it's not there, you may
add the cwd to your path:
PATH=$PATH:.
or you must use './' when issuing a command in th cwd, try:
./configure
make
2: LILYPOND Windows-NT Support -- by Jeffrey Reed
My point of reference comes from 15 odd years working with a
variety of UNIX platforms. I am relatively new to Windows-
NT and, even though I am a card carrying UNIX bigot, I am
excited about the NT OS. My goals for lilypond are to give
back to the Free Software Foundation a little of what they
have given me over the years and to contribute to the lily-
pond project by supporting a Windows-NT port. I hope that
someday we can distribute and run lilypond on the NT OS in a
much more native fashion.
o Building lilypond on Windows-NT
o Maintaining lilypond on Windows-NT
o Running lilypond on Windows-NT
2.1: Building lilypond on Windows-NT
Currently as stated above lilypond is primarily a UNIX
thing. The Windows-NT port is based on the UNIX environment
provided by Cygnus. Therefore the first step is to download
and install the Cygnus development kit:
2.1.1: Cygnus Development Kit
http://www.cygnus.com/misc/gnu-win32/
Please follow the documentation Cygnus has on there web site
for downloading and installing. The important part is that
you down load the entire development kit. I believe it is
full.exe. The installation will ask you where you want to
install it. I will refer to Cygnus installation directory
as /gnuwin32/cygwin-b20. There should be a README file that
contains installation instructions. After the installation
is complete you should have a Cygnus shortcut in your Pro-
gram section of your Start Menu. This shortcut is your door
to the UNIX world and I will refer to the resulting window
as a bash shell.
The shortcut points to /gnuwin32/cygwin-b20/cygnus.bat. The
following is my cygnus.bat file.
@ECHO OFF
rem default environment
rem GNU cygnus installation
SET CYGREL=B19.1
SET MAKE_MODE=unix
SET LOCAL_ROOT=d:\gnuwin32
SET LOCAL_FS=d:/gnuwin32
SET LOCAL_DIR=d:/gnuwin32/cygwin-b20
SET CYGROOT=%LOCAL_ROOT%\cygwin-b20
SET CYGFS=%LOCAL_FS%/cygwin-b20
SET TCL_LIBRARY=%CYGROOT%\share\tcl8.0
rem
rem This was not in the original but is needed by lots of packages
rem
SET BISON_SIMPLE=%CYGFS%/share/bison.simple
rem
rem I place the cygnus stuff in front of /WINNT
rem
SET PATH=d:\bin;%LOCAL_ROOT%\bin;%CYGROOT%\H-i586-cygwin32\bin;%PATH%
SET MANPATH=%LOCAL_ROOT%\man;%LOCAL_ROOT%\cygwin-b20\full-man\man
SET
INFOPATH=%LOCAL_FS%/cygwin-b20/full-man/info;%LOCAL_FS%/cygwin-b20/info;%LOCAL_DIR%/info
rem General tools not included with Cygnus Development Kit
rem CVS
SET PATH=%PATH%;%LOCAL_ROOT%\cvs-1.9.28\bin
SET INFOPATH=%INFOPATH%;%LOCAL_FS%/cvs-1.9.28/info
SET MANPATH=%MANPATH%;%LOCAL_ROOT%\cvs-1.9.28\man
rem EMACS
SET PATH=%PATH%;%LOCAL_ROOT%\emacs-19.34\bin
SET INFOPATH=%INFOPATH%;%LOCAL_FS%/emacs-19.34/info
rem VIM
SET VIM=%LOCAL_ROOT%\vim-4.6\doc
SET PATH=%PATH%;%LOCAL_ROOT%\vim-4.6
rem TeX
SET PATH=%PATH%;%LOCAL_ROOT%\texmf\miktex\bin
rem a2ps
SET PATH=%PATH%;%LOCAL_ROOT%\a2ps-4.10\bin
SET INFOPATH=%INFOPATH%;%LOCAL_FS%/a2ps-4.10/info
SET MANPATH=%MANPATH%;%LOCAL_ROOT%\a2ps-4.10\man
rem python
SET PATH=%PATH%;\Program Files\Python
rem perl
SET PATH=%PATH%;\qub
rem yodl
SET PATH=%PATH%;%LOCAL_ROOT%\yodl-1.30.0.pre10\bin
set MANPATH=%MANPATH%;%LOCAL_ROOT%\yodl-1.30.0.pre10\man
uname -sv
bash -login
Please look over this carefully. Be careful with the forward
and backward slash notations. The paths specified were done
for good reasons. Maybe someday we will all be using UNC.
Note the BISON entry and the PATH ordering in particular.
Also note that the generic cygnus.bat you will be looking at
does not include alot of the packages listed. We will be
installing some of these.
The installation also suggests that you create a directory
/bin and copy /gnuwin32/cygwin-b20/H-i586-cyg-
win32/bin/sh.exe to /bin. The sh.exe shell provided by
Cygnus is a descendant of the ash shell. The sh.exe shell
has improved greatly and is much faster than the bash shell
for script invocations. So this is my recommendation for
post installation steps. From a bash shell:
o cd /
o mkdir bin
o cd /bin
o cp /gnuwin32/cygwin-b20/H-i586-cygwin32/bin/sh.exe
sh.exe
o cp /gnuwin32/cygwin-b20/H-i586-cygwin32/bin/bash.exe
bash.exe
o cd /
o mkdir /tmp
o chmod a+rwx tmp
o mkdir /etc
o cd /etc
o mkpasswd -l > passwd
o mkgroup -l > group
Binary Mounts
There is also some discussion of how you want to mount the
Cygnus development kit. mount is a UNIX term that refers to
the mechanism used to provide a disk resource to the
filesystem. Cygnus supplies a mechinism for mounting a
filesystem as a DOS like resource or a UNIX like resource.
Among other things this attempts to deal with the text file
carriage return line feed on DOS versus the line feed on
UNIX and the issue that DOS has two file types, text and
binary. Where UNIX deals with a single streams type. My
opinion on this matter currently is to use binary mounts
only. This can be accomplished by:
o From a bash shell, umount /
o mount -b d: /
If you have other disks that you intend to use for data gen-
erated by cygnus tools you will have to mount those devices
with the -b switch.
2.1.2: Ecgs Compiler, assembler, and linker
http://www.xraylith.wisc.edu/~khan/software/gnu-
win32/egcs.html
Cygnus now distributes the ecgs compiler with cygwin-b20.
2.1.3: GNU's Internationalization Package
http://www.gnu.org/order/ftp.html
Considering the origin of the major contributors of lily-
pond, this is a must. However before we actually do a GNU
build we have to discuss some caveats of the Windows-NT OS
in particular the naming of executable files. Windows-NT
uses a .exe extension where UNIX does not use an extension.
This causes a problem during the installation portion of a
GNU build. The following script can be used to help allevi-
ate this problem.
#!/bin/sh
realinstall=/gnuwin32/cygwin-b20/H-i586-cygwin32/bin/install.exe
args=''
while [ $# -ne 0 ]
do
case $1 in
-*) args="$args $1"
;;
*) if [ -f $1.exe ]; then
args="$args $1.exe"
else
args="$args $1"
fi
;;
esac
shift
done
$realinstall $args
I place this in script ~/bin. The LilyPond configure,
build, and install process handles this with it's own
install script. In addition there are patches to the cygnus
install command that also deals with this problem. Having
said that, here is how one might build the gettext package.
o download the package from one of the ftp sites.
o From a bash shell, cd ~/usr/src.
o tar zxf gettext-0.10.tar.gz
o cd gettext-0.10
o ./configure --prefix=$CYGFS/H-i586-cygwin32
o make
o make install
2.1.4: GNU's roff package
http://www.gnu.org/order/ftp.html
Following the instructions for gettext package to download,
build, and install the groff package.
2.1.5: Python Programing Language
http://www.python.org
Python is the scripting language of choice for a lilypond
build. There is a native Windows-NT self extracting binary
distribution available. I recommend installing Python in a
directory that does not have spaces. And then place it in
the bash shell path by editing $CYGFS/cygnus.bat.
2.1.6: Perl Programing Language
http://www.cpan.org
I believe perl is used in some legacy scripts to date.
There is a native Windows-NT self extracting binary distri-
bution available. I recommend installing Perl in a direc-
tory that does not have spaces. And then place it in the
bash shell path by editing $CYGFS/cygnus.bat.
2.1.7: Yodl Document Language
http://www.xs4all.nl/~jantien/yodl/
Yodl for documentation in LilyPond. It is currently being
updated by Jan Nieuwenhuizen. The development methodology
of Yodl as well as LilyPond relies on a the following direc-
tory structure:
$HOME/usr/src/
|-releases/
|-patches/
|-test/
releases/
Downloaded and generated releases live here. For exam-
ple yodl-1.31.7.tar.gz and lilypond-1.1.17.tar.gz.
patches/
Downloaded and generated patches live here. For exam-
ple yodl-1.31.7.diff.gz and lilypond-1.1.17.diff.gz.
test/
This directory is used to generate releases and
patches.
I strongly recommend using this file structure to build yodl
and lilypond.
o download the package from
http://www.xs4all.nl/~jantien/yodl/ to
$HOME/usr/src/releases.
o From a bash shell, cd $HOME/usr/src.
o tar zxf releases/yodl-<version>.tar.gz
o cd yodl-<version>
o ./configure --prefix=/gnuwin32/yodl-<version>
--srcdir=. Since yodl is under development I choose to
install it in a version rooted directory. This allows
me to test newly released versions without losing a
known working version.
o make
o make install
o place it in the bash shell path by editing
$CYGFS/cygnus.bat. For example:
rem yodl
SET PATH=%PATH%;%LOCAL_ROOT%\yodl-1.31.7\bin
2.1.8: guile
GUILE, GNU's Ubiquitous Intelligent Language for Extension,
is a library that implements the Scheme language plus vari-
ous convenient facilities. It's designed so that you can
link it into an application or utility to make it extensi-
ble. GNU's plan is to link this library into all GNU pro-
grams that call for extensibility.
o download guile-1.3 patch from
http://home.austin.rr.com/jbr/jeff/lilypond/guile.patch
and save it to /tmp/guile.patch.
o download guile-1.3 from one of GNU's ftp sites.
o From a bash shell, tar zxf guile-1.3.tar.gz
o cd guile-1.3
o patch -p2 < /tmp/guile.patch
o LD=/gnuwin32/cygwin-b20/H-i586-cygwin32/bin/ld \
./configure --prefix=$CYGFS/H-i586-cygwin32
o make sure bin_PROGRAMS macro in libguile/Makefile does
not have the .exe extension during the build
o make
o make sure bin_PROGRAMS in libguile/Makefile does have
the .exe extension during the install. Yuck.
o make install
2.1.9: LilyPond
o download the package from http://www.cs.uu.nl/peo-
ple/hanwen/lilypond/ to $HOME/usr/src/releases.
o From a bash shell, cd $HOME/usr/src.
o tar zxf releases/lilypond-<version>.tar.gz
o cd lilypond-<version>
o ./configure --prefix=/gnuwin32/lilypond-<version> \
--srcdir=.
Since lilypond is under development I choose to install
it in a version rooted directory. This allows me to
test newly released versions without losing a known
working version.
o make
o make install
o place it in the bash shell path by editing
$CYGFS/cygnus.bat. For example:
rem lilypond
SET PATH=%PATH%;%LOCAL_ROOT%\lilypond-1.1.17\bin
2.2: Maintaining lilypond on Windows-NT
If you have built lilypond on Windows-NT using the directory
structure described previously and the process described in
section 2.1.9, then you are ready to maintain lilypond. It
can not be that easy!? Well, there is one caveat. Cur-
rently to use the stepmake/bin/release.py and step-
make/bin/package-diff.py scripts you need to obtain/build a
version of python that was built with Cygnus development
kit. The process I used is as follows:
o obtain python source from http://www.python.org
o tar zxf /tmp/python-<version>.tar.gz
o cd python-<version>
o configure --prefix=/gnuwin32/Python-<version>
o edit toplevel Makefile EXE macro so it reads EXE=.exe
o make
o make install
o place it in the bash shell path by editing
$CYGFS/cygnus.bat. For example:
rem python
SET PATH=%PATH%;%LOCAL_ROOT%\python-1.5.1\bin
I choose to build lilypond with the standard Windows-NT
python and use the Cygnus version for using the release
scripts. This way I can make sure the Windows-NT python
version is able to build lilypond. Currently there are sev-
eral issues with the release scripts. Using os.link and
os.system(set -x;...) are to name a few.
To generate a new release and patch you must use the direc-
tory structure described previously. And follow the
instructions found in PATCH.txt. Editing Documenta-
tion/AUTHORS.yo, VERSION, and NEWS is also required. When
my edits are complete and tested I:
o Edit config.make and change python path to the Cygnus
version: PYTHON=/gnuwin32/Python-1.5.1/bin/python.
o make release
The new release is placed in releases directory and the
patch is placed in the patches directory. I email the new
patch to [EMAIL PROTECTED] More than one patch a
day can be generated by:
o cd $HOME/usr/src
o tar zxf releases/lilypond-<version>.<patchlevel>
o use your normal configure
o make edits
o Change VERSION to increment <patchlevel>
o Change NEWS
o make release
2.3: Running lilypond on Windows-NT
We are now distributing a formated binary distribution for
Windows-NT. Please refer to
http://home.austin.rr.com/jbr/jeff/lilypond/ for current
news, download, installation, and running information.
Jeffrey B. Reed [EMAIL PROTECTED]
3: RUNNING LILYPOND -- by Dominique Cretel
You may want to refer to section 2.3, for more current
information about downloading, installing, and running the
Windows-NT binary distribution.
1. First, I have download tha 0.1.64 version of LilyPond
music software.
2. Then I extract it in a temp directory, and I move the
directory "lilypond-0.1.64" to the root directory of my
D drive.
3. I go to the D:\Lilypond-0.1.64\tex directory to modify
the lilyponddefs.tex file (lines 75 and 84), and com-
ment all cmbx15 ans cmbx14, and replace them by cmbx12.
4. build a command file like this: Note: I use MiKTeX to
process the tex file generated.
---begin ly2dvi.bat
echo off
set ver=0.1.64
set path=%path%;d:\lilypond-%ver%\bin
lilypond -I d:\lilypond-%ver%\init %1
rem *** pause
set path=c:\texmf\miktex\bin;%path%
set TEXINPUTS=%TEXINPUTS%;d:\lilypond-%ver%\tex
set MFINPUTS=%MFINPUTS%;d:\lilypond-%ver%\mf
tex %1.tex
rem *** pause
dvips %1.dvi
rem *** pause
set path=%path%;d:\gstools\gsview
gsview32 %1.ps
---end ly2dvi.bat
5. execute lilypond by doing:
ly2ps silly <Enter>
Note:
You'll better have to put the SET commands lines in a sepa-
rate command file to avoid consumming each time environnment
ressources.
Bye,
Dominique Cretel [EMAIL PROTECTED]
4: PROBLEMS AND ANWSWERS
4.1: CONFIGURE AND INSTALL
This is all to confusing. I have:
1. downloaded /tmp/lilypond-0.1.78.tar.gz
2.
cd ~/usr/src
3.
tar zxf /tmp/lilypond-0.1.78.tar.gz
4.
./configure --prefix=/users/jeff/lilypond-0.1.78
\--enable-tex-prefix=/users/jeff/lilypond-0.1.78/texmf
\--enable-tex-dir=/users/jeff/lilypond-0.1.78/texmf/tex
\--enable-mf-dir=/users/jeff/lilypond-0.1.78/texmf/mf
5.
make
6.
make install
I did have a problem with lilypond.info. And I will look
into this further. After mending lilypond.info issue, it
compiled and install with no problems.
I have 64 Meg of physical memory and 64 Meg of swap. Actu-
ally I need to increase the swap space. If a memory problem
is occuring it most likely is during the link process of
lilypond. There is a boat load of objects to link.
Jan the mount -b stuff is confussing to me. I have the
entire system mounted _without_ -b and only use -b on cer-
tain paths for programs that create binary files that do not
use O_BINARY open option. By the way the midi file open is
one of these cases, I need to look into that. I have had no
problems with this methodology.
4.2: DRIVE D:
The windows multiroot filesystem is an utterly broken con-
cept. Please do everything on one (urg) drive, C:.
> configure
> creating cache ./config.cache
> [..]
> creating config.make
> creating config.hh
> cd: lstat /d failed
Ok, this looks like another stupid windows problem. You're
working on 'drive D:', right?
I can think of some solutions, but i don't know if they
work; i just had to do some work in windows some time ago.
If you have problems with this, please ask gnu-
[EMAIL PROTECTED] I'll start with the simplest:
o do everything on drive C:, or
o explicitely mount drive d:, work from there:
mkdir -p /mnt/d
mount d: /mnt/d
cd /mnt/d/lilypond-x.y.z/
o make d:/ the root of cygnus, in cmd.exe/command.exe do:
umount /
mount d: /
4.3: INSTALLING TOOLS
> - First I have installed Python (for win32) "Pyth151.exe"
and "Configure
> don't find it. I had to put it in the path for configure
find it?
Yes, of course. It should be possible to have different
versions of tools installed (e.g. perl 4 and perl 5). The
best way to tell people (or tools like configure) which one
to use is to put it in the path?
Another small unix lesson: Where under dos each program
installs itself into a nice directory
c:\DosProgram\*
under unix, installation is handled centrally. Executables
go in /usr/bin (or /usr/local/bin), and are always in your
path.
4.4: VIRTUAL MEMORY
> 4. make -C lily don't work. I get an error (see below). I get several
> object files in the ./lily/out directory (34 files: 17 *.dep, 16 *.o,
> and 1 *.hh):
> [...]
> include/engraver-group.hh:35: virtual memory exhausted
> make: *** [out/bar-grav.o] Error 1
> bash-2.01$
Ok, so everything works now, there's only some error with
one of the source files. Lets see which one (and now the
cc's now why they're reading this :-)
It looks like you've run out of memory. You should compile
without optimisation, gcc/egcs need a lot of memory for
optimising. Reconfigure without optimisation:
configure --disable-optimise
or edit config.make:
## USER_CXXFLAGS = -g # -O no optimise!
USER_CXXFLAGS = -g
There are some other things to look at: how much RAM do you
have (please say something > 8Mb :-)? Although it might be
an egcs bug, you should have a look at the size of your swap
file. For an US version of windows, you should find it
here:
/start/settings/control-panel/system/performance/virtual-memory
you see, amongst others, these entries:
paging file size for selected drive:
space-available: xx
initial-size: xx
maximum-size: xx
total paging file size for all drives
currently allocated: xx
Try to set:
initial-size: 64
maximum-size: 128
Make sure that:
o maximum-size >= 128 Mb
o urrently-allocated + space-available >= 128 Mb
