[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: HOWTO: lilypond-1.3.98 on windows32

From: janneke
Subject: Re: HOWTO: lilypond-1.3.98 on windows32
Date: 25 Oct 2000 10:32:46 +0200

"James Hammons" <address@hidden> writes:

> I guess what I'm trying to say is that it's simpler in that you don't need
> to install Cygnus *at all* in order to use the win32 version of lily on
> windows.

Ok.  What I'm trying to say is that, while it may be less work not to
install cygwin if you know what you're doing, it is more error prone,
and will generate bug reports and questions.  What unpack program
will people use, and what bugs will it have.  Can it be automated?
etc.  Also, bug reports will come anyway, but if people used at least
tar, gzip to install, and have bash and guile running, I'd be able
to help.

Once you have cygwin installed, which should be real easy, we can
provide simple lily-install and lily-upgrade scripts.  I'd
hoped/expected  for someone with a windows box to have written and
supplied these.  I haven't done that, mainly because I didn't have
access to a windows box, and small mistakes will creep in.


   mkdir -p $cache
   for i in $packages; do
        if [ -f $cache/$i* ]; then
                echo $cache/$i* exists, skipping
                wget --directory-prefix=$cache $archive/$i*.tar.gz

   ln -sf / /Cygwin
   for i in $packages; do
        tar -C / -xzvf $cache/$i*

   " $packages 98
   file=`ls -t1 $cachelilypond-1.3.9* | head -1`
   latest=`expr $x : ".*lilypond-1[.]3[.]\([^.]*\).*.tar.gz"` $((latest + 1))

   if [ -z $patchlevel ]; then
   fi lilypond-1.3.$patchlevel

   echo "Please add /Cygwin/usr/lilypond-1.3.$patchlevel/bin to your path"

Ok, now this is in now way fool-prove, but it should work for most
people.  You'll get all cygnus stuff in /Cygwin, and lilyponds in
/Cygwin/usr/lilypond-x.y.z/.  Why would that not work for you?

If you add logging to the scripts, people that have troubles
just send in the log.  If you don't install cygwin, and let new users
choose their own directories; it'll save them a fairly simple
download, but cause us all a lot of trouble.

> And I'm able to keep different versions alongside each other as
> well using this setup, switching between them easily by executing the
> appropriate batch file.

Don't write batch files, use bash.  

> Basically, I have a "lilypond" directory tucked away on my hard drive
> somewhere that contains a "music" subdirectory (that holds the different
> lily version setup batch files and .ly files that I & others have written)
> and a "Cygwin.nn" subdirectory (that holds the latest win32 version of lily)
> where nn is the patch level.  Since I generally purge the unstable versions,
> I'm left with a nice set of compact, easy-to-switch-between lilypond
> installs.  It may not be optimal from a unix point of view, but it's the way
> that I like to organize things on my machine.  Your mileage may vary...  :-)

What you'd like to do is fine, of course (even though I don't get
it).  But it would be good to suggest and provide uniform + debuggable
install method for the newbie.

> I guess I should add the following disclaimer to the end of my HOWTO:

Well, yesterday was a bad day for me, and all the windows troubles
taking so much time just depressed me more.  I would much more like it
if you'd try to use my suggestions yourself, and help debug + document
that.  We'll get bug reports/help requests anyway.


Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter       |

reply via email to

[Prev in Thread] Current Thread [Next in Thread]