lilypond-devel
[Top][All Lists]
Advanced

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

Re: devel on OSX


From: Matthias Neeracher
Subject: Re: devel on OSX
Date: Tue, 27 Jul 2004 17:31:19 -0700


On Jul 27, 2004, at 4:40 PM, Graham Percival wrote:
g++ -shared -o out/midi.so out/midi.lo -L/sw/lib -L/sw/lib -lguile -lguile-ltdl -lm
g++: unrecognized option `-shared'

There are also parts of lilypond.patch that you'll need to apply. Specifically here the patch would be, I think:

Ok.

Should this be considered a bug? I mean, isn't this kind of patch that configure is made to deal with?

Conceptually, yes, that's something the GNU tool chain can handle. Specifically, this would be handled by libtool. However, libtool is, as far as I understand it, an all or nothing proposition, and using it is not entirely trivial.

I'm not complaining; it's just that once I've succeeded in making Lilypond, I'll add the notes to INSTALL.txt for other potential OSX Lilypond developers. Should OSX developers be patching certain files manually, or can the basic Lilypond source tarball be modified to allow for this?

It's my understanding that the basic Lilypond distribution eventually will move to a portable build system. At that time, I should go through my patch and sort out the various issues (I've last done this last year, and contributed some minor patches to the basic distribution). Many of the patches have to do with the way that fink likes to have things laid out; IMHO, this is not really something that belongs in the basic tarball.

Matthias





reply via email to

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