Re: Problems compiling trunk on OS X 10.5

2009-08-30 Thread Graham Percival
On Sun, Aug 30, 2009 at 11:04:43PM -0400, Travis Briggs wrote: > Which is to say, I have successfully compiled the lilypond trunk > (2.13.4) on Mac OS X 10.5.8 (Leopard) x86 Intel. > > Thanks for the help, I'll write up a step-by-step of what I did > tomorrow and post it. That won't be useful --

Re: Problems compiling trunk on OS X 10.5

2009-08-30 Thread Patrick McCarty
On 2009-08-30, Travis Briggs wrote: > > Also I've run into further issues, since my > /opt/local/share/ghostscript/fonts/ doesn't contain any of the c0590* > files. Ah, this might be a problem too... What are the names of the Century Schoolbook L fonts you had installed in that directory (before

Re: Problems compiling trunk on OS X 10.5

2009-08-30 Thread Patrick McCarty
On 2009-08-30, Travis Briggs wrote: > I used the git command in the INSTALL document > (http://lilypond.org/doc/v2.13/Documentation/topdocs/INSTALL.html#Downloading-source-code) > > git clone git://git.sv.gnu.org/lilypond.git > > In my configure script, I have the following at line 4547: > > if

Re: Problems compiling trunk on OS X 10.5

2009-08-30 Thread Travis Briggs
It's alive! It's alive! Which is to say, I have successfully compiled the lilypond trunk (2.13.4) on Mac OS X 10.5.8 (Leopard) x86 Intel. Thanks for the help, I'll write up a step-by-step of what I did tomorrow and post it. -Travis On Sun, Aug 30, 2009 at 10:40 PM, Travis Briggs wrote: > I use

Re: Problems compiling trunk on OS X 10.5

2009-08-30 Thread Travis Briggs
I used the git command in the INSTALL document (http://lilypond.org/doc/v2.13/Documentation/topdocs/INSTALL.html#Downloading-source-code) git clone git://git.sv.gnu.org/lilypond.git In my configure script, I have the following at line 4547: if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_tes

Re: Problems compiling trunk on OS X 10.5

2009-08-30 Thread Patrick McCarty
On 2009-08-30, Travis Briggs wrote: > Here's an update: > > I found the following in config.make: > NCSB_SOURCE_FILES = /Library/Fonts/Hei.dfont /Library/Fonts/Hei.dfont > /Library/Fonts/Hei.dfont /Library/Fonts/Hei.dfont > > Looks like my fc-match was returning that because it was from > foundry

Re: Problems compiling trunk on OS X 10.5

2009-08-30 Thread Travis Briggs
Here's an update: I found the following in config.make: NCSB_SOURCE_FILES = /Library/Fonts/Hei.dfont /Library/Fonts/Hei.dfont /Library/Fonts/Hei.dfont /Library/Fonts/Hei.dfont Looks like my fc-match was returning that because it was from foundry=urw. I didn't have the NCSB fonts in a place that l

[PATCH] Improve `make distclean' behavior

2009-08-30 Thread Patrick McCarty
Hi, Attached is a patch that modifies `make distclean' so that it behaves correctly. I've thoroughly tested it, though I've never modified any of the makefiles before, so I'm naturally a little hesitant about it. Okay to apply? Thanks, Patrick >From 9adf95e3566d4e3e14a59c412541d106cf020309 Mon

Re: Calling functions defined in a .scm file in a .ly file

2009-08-30 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Sonntag, 30. August 2009 20:59:56 schrieb Nicolas Sceaux: > Le 30 août 09 à 14:44, Reinhold Kainhofer a écrit : > > I tried inserting > > #(use-module (scm display-lily)) > > in my .ly file, but that didn't work at all. > > The note-name->lily-stri

Re: Problems compiling trunk on OS X 10.5

2009-08-30 Thread Graham Percival
On Sun, Aug 30, 2009 at 02:06:11PM -0400, Travis Briggs wrote: > I'm following the instructions on > http://lilypond.org/doc/v2.13/Documentation/topdocs/INSTALL.html Those instructions may be out of date. Could you compare them to these two pages: http://ivo.bouwmans.name/lilypondleopard/ http://

Re: Calling functions defined in a .scm file in a .ly file

2009-08-30 Thread Nicolas Sceaux
Le 30 août 09 à 14:44, Reinhold Kainhofer a écrit : I'm struggling with how to access a function that is define- public'ed in an scm file. In particular, the file define-music-display-methods.scm defines the note-name->lily-string function to return a human-readable representation of the giv

Problems compiling trunk on OS X 10.5

2009-08-30 Thread Travis Briggs
Hi, I'm following the instructions on http://lilypond.org/doc/v2.13/Documentation/topdocs/INSTALL.html I've installed all required dependencies using macports. I've also done 'export LD_LIBRARY_PATH=/opt/local/lib' to get around: "libguile-srfi-srfi-1-v-3", message: "file not found" Now I'm stu

[PATCH] Re: Add $currentbook and $currentbookpart parser variables

2009-08-30 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Sonntag, 30. August 2009 12:05:18 schrieb nicolas.sce...@gmail.com: > I think $currentbook and $currentbookpart (which might be hyphenized) > ought to be initialized to #f in ly/init.ly, as $defaultheader is, and > set to #f and the end of \book* bl

Calling functions defined in a .scm file in a .ly file

2009-08-30 Thread Reinhold Kainhofer
I'm struggling with how to access a function that is define-public'ed in an scm file. In particular, the file define-music-display-methods.scm defines the note-name->lily-string function to return a human-readable representation of the given pitch. Now, I want to call that from a custom function

[PATCH] Re: Add $currentbook and $currentbookpart parser variables

2009-08-30 Thread Reinhold Kainhofer
> Concerning the issue: > >"There is still a problem with bookpart not using the $defaultheader > starting with the second bookpart..." > > The code is in book.cc, void Book::set_parent (Book *parent). > It was made on purpose, but as it turns out, that was probably a bad > idea. Yes, I th

Re: [PATCH] Re: Creating books with Scheme

2009-08-30 Thread Nicolas Sceaux
Le 30 août 09 à 03:20, Carl Sorensen a écrit : On 8/29/09 7:01 PM, "Reinhold Kainhofer" wrote: You mean something like this patch: http://codereview.appspot.com/112044 LGTM. Just a question. In your regression test, you first define (add-one- score #f), then you set! it to a

Re: funky build errors

2009-08-30 Thread Patrick McCarty
On 2009-08-30, Werner LEMBERG wrote: > > > Here are my configuration settings for FontForge on a i586 GNU/Linux > > box: [...] > > > > --enable-double > > IIRC, this option is the very one which makes the problems disappear. > Hmm. Perhaps it's better to write to the various distri