bug-lilypond
[Top][All Lists]
Advanced

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

Re: Issue 504 in lilypond: lilypond broken on osx 10.5 x86


From: Hans Aberg
Subject: Re: Issue 504 in lilypond: lilypond broken on osx 10.5 x86
Date: Sun, 16 Dec 2007 15:14:25 +0100

On 16 Dec 2007, at 13:17, Graham Percival wrote:

You almost certainly have Xcode installed, though. Of course this will give you make, but we can't rely on normal users having xcode installed.

Yes, in Mac OS X 10.4 one must have Xcode to get the compilers, and I would think it is the same in Mac OS X 10.5. Even though Xcode may come on the installation discs, one must sign up as an Apple developer (which is for free) to get the updates, which is recommended to avoid bugs. But if Xcode is installed, and LilyPond compiles, it should be easy to provide binaries for distribution. Also, I switched to using Xcode as an editor for text files, including the LilyPond files. It handles Unicode characters in UTF-8 well, so it is all I need.

So, as for LilyPond, I think the starting point is to get it work in the traditional UNIX sense with "make", and an installation in /usr/ local/. You might still use a traditional application-like installation, putting all stuff in directories named /usr/local/ lilypond-<version>, and then one can set soft links or set environment variables to access programs. This way one can easily have several versions installed (like development and latest stable), and it is easy to remove old ones, as it is all contained in a single directory. I would not mind also having the latest documents in such a distribution, as LilyPond gets frequent new updates, and it simplifies getting the latest version of it all.

One idea that comes to my mind from a program called "modules" <http://modules.sourceforge.net/>, is that one may have a program called say "lilypond-version" that sets an environment variable, selecting the lilypond versions to use. For example "lilypond-version stable", "lilypond-version development", "lilypond-version cvs", "lilypond-version 2.11.34", or whatever, and if the version exists installed, it is selected, otherwise one gets an error message. This way, one can easily try different versions.

And while it, perhaps another program, "lilypond-update" that checks for new version, and in the long run makes the installation.

Just some inputs :-).

  Hans Ã…berg






reply via email to

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