Hi lads,

Tonight, I tried mingw, but it won't work.  For real straightforward
use, I'm waiting for Cygnus' upcoming net release, when the .dll's
will all be in sync again.

Anyway, for you who haven't given up already, there's a new release
with some fixes:

    * buildscripts/make-cygwin-cross.sh: A try at dropping cygwin1.dll
     dependency by using mingw.  Compiling guile is too much to ask
     for mingw, though.  Also:
     - rename python scripts .py (request from Alain)
     - install native packages under their own, separate root. (Alain)

    * lily.scm: Don't use regex module when running on
    Windows. (Shamus)


Go get it from:

    http://appel.dyndns.org/lilypond/gnu-windows/


Also, I've put this README up:

Experimental binary for GNU/Windows, using Cygnus' gnu-windows package.

LilyPond uses Guile, and needs *this* cygwin1.dll, so get them all tree.
(If you have already downloaded guile or the dll from this place, you
only need to get a fresh lilypond).

If you don't install in the root directory of your cygnus installation
(that's where '/' is mounted), you'll have to set these:

    export LILYPONDPREFIX=<your_root>/Cygnus/lilypond-x.y.z/usr/share/lilypond
    export GUILE_LOAD_PATH=<your_root>/Cygnus/guile-1.3.4/usr/share/guile/1.3.4

(if you don't use bash, but a strictly dos compatible shell, use
 `set' for `export' and change '/' to '\').

Until Cygnus' new release (any day now) comes out, you'll need the
supplied cygwin1.dll too.  This is nasty, because your other cygwin
binaries (b20.1) need their own cygwin1.dll, and they conflict.

What you probably can do is, if you run bash:

    * don't put lilypond in your path
    * assuming lilypond.exe is in /Cygnus/usr/lilypond-1.3.39/usr/bin,
      put the supplied cygwin1.dll there too
    * run lilypond on foo.ly:
         c:\>bash
         $ PATH=/Cygnus/usr/lilypond-1.3.39/usr/bin:$PATH lilypond.exe foo.ly 
    * have someone automate this for you into a script

By the way, for those of you who don't have TeX up and running, you should
be able to view some output doing:

    lilypond -f ps foo.ly
    export GS_FONTPATH=/Cygnus/usr/lilypond-x.y.x/share/lilypond/pfa
    gv foo.ps


Most information in the .html files is probably obsolete.

Greetings,

Jan.

-- 
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org

Reply via email to