Proposed patch: configure version number checking
I hadn't tried to build 2.9.x in a while, and it seems that there was a change to the version number checking that broke for some of the tools used in the fink build on MacOS X. e.g. we run guile-config as guile-1.6-config. The solution is to insist that the version number be at the beginning of a line or after a space (a 1 character patch – does it get any more efficient than that?) Matthias diff -ruN lilypond-2.9.16-orig/aclocal.m4 lilypond-2.9.16/aclocal.m4 --- lilypond-2.9.16-orig/aclocal.m4 2006-08-26 20:47:16.0 -0700 +++ lilypond-2.9.16/aclocal.m4 2006-08-26 21:43:45.0 -0700 @@ -34,7 +34,7 @@ ## grab the first version number in --version output. eval _ver=\\`($1 --version || $1 -V) 21 | grep '\(^\| \) [0-9][0-9]*\.[0-9]' \ | head -n 1 \ - | tr ' ' '\n' | grep '[0-9]\.[0-9]' | head -n 1 | sed 's/\ ([0-9.]*\).*/\1/g'\`\ + | tr ' ' '\n' | grep '^[0-9]\.[0-9]' | head -n 1 | sed 's/\ ([0-9.]*\).*/\1/g'\`\ if test -z $_ver; then ## If empty, try date [fontforge] ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Proposed patch: configure version number checking
Please take a look a the mailing list archives for bug-lilypond and lilypond-devel to see what kind of different situations that the previous version number checks failed on, before proposing yet another change. /Mats Quoting Matthias Neeracher [EMAIL PROTECTED]: I hadn't tried to build 2.9.x in a while, and it seems that there was a change to the version number checking that broke for some of the tools used in the fink build on MacOS X. e.g. we run guile-config as guile-1.6-config. The solution is to insist that the version number be at the beginning of a line or after a space (a 1 character patch – does it get any more efficient than that?) Matthias diff -ruN lilypond-2.9.16-orig/aclocal.m4 lilypond-2.9.16/aclocal.m4 --- lilypond-2.9.16-orig/aclocal.m4 2006-08-26 20:47:16.0 -0700 +++ lilypond-2.9.16/aclocal.m4 2006-08-26 21:43:45.0 -0700 @@ -34,7 +34,7 @@ ## grab the first version number in --version output. eval _ver=\\`($1 --version || $1 -V) 21 | grep '\(^\| \) [0-9][0-9]*\.[0-9]' \ | head -n 1 \ - | tr ' ' '\n' | grep '[0-9]\.[0-9]' | head -n 1 | sed 's/\ ([0-9.]*\).*/\1/g'\`\ + | tr ' ' '\n' | grep '^[0-9]\.[0-9]' | head -n 1 | sed 's/\ ([0-9.]*\).*/\1/g'\`\ if test -z $_ver; then ## If empty, try date [fontforge] ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
\transposedCueDuring
With the command \transposedCueDuring a cue's transposition can be
changed locally. This can be used to prevent excessive ledger lines on
cues.
Could somebody create a short example of this so I can include it in the
manual? The only docs that exist for it right now is
ly/music-functions-init.ly:
Insert notes from the part @var{what} into a voice called @code{cue},
using the transposition defined by @var{pitch-note}. This happens
simultaneously with @var{main-music}, which is usually a rest. The
argument @var{dir} determines whether the cue notes should be notated
as a first or second voice.
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond ChangeLog Documentation/user/examples....
Quoting Graham Percival [EMAIL PROTECTED]:
Han-Wen Nienhuys wrote:
-A number followed by a period is interpreted as a real number, so
-for setting the tempo for dotted notes, an extra space should be
-inserted, for example
-
[EMAIL PROTECTED]
-\midi @{ \tempo 4 . = 120 @}
[EMAIL PROTECTED] example
Is this really the new way to do it?
\midi {
\context {
\Score
tempoWholesPerMinute = #(ly:make-moment 120 4)
}
}
I'm sure that there's some reason why \tempo x = y is a horrible
construct and must be replaced, but
\context {
\Score
tempoWholesPerMinute = #(ly:make-moment y x)
}
looks unnecessarily complicated. If that's the way it's going to be,
I'll document it, but... why this? Do we want to allow users to have
different tempo in different Staff contexts?
Apart from looking complicated, I find it directly confusing. If you
told me that the property name was tempoWholesPerMinute, I would
intuitively expect the value to be a real number. Here it seems that we
(mis)use ly:make-moment to represent a rational number. Of course,
that's convenient as long as the beat isn't a dotted note, since you
can just set x as the
duration of the beat, but it still requires quite some amount of
thinking the first time you see it.
/Mats
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: changing the midi instrument; broken
On Sunday 27 August 2006 07:26, Graham Percival wrote: Ted Walther wrote: The documentation of lyrics has got me befuddled on the notion of contexts, as I haven't seen anywhere it clearly says what I can do in lyricsmode that I can't do in lyricsto, although the documentation does state that there is a difference. Perhaps the complete read-through of the manual will clear it up. If you figure it out, let me know. I don't use vocal music, so I've barely touched that section. I'm happy for corrections, though. In short: \lyricmode is just a marker that says the following input characters should be interpreted as lyrics, rather than notes. \lyricsto is a function, which aligns lyrics to notes. So in \lyricsto you need a voice to align lyrics to, while in \lyricmode you need to specify the duration of each syllable manually. So: You always want to use lyricsto, but if you want to store a line of lyrics in a variable, use lyricmode and then use lyricsto to align that variable to music. -- Erik ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB success.
On Saturday 26 August 2006 21:51, Erik Sandberg wrote: On Saturday 26 August 2006 01:07, Han-Wen Nienhuys wrote: Erik Sandberg wrote: - I could temporarily fix the above problem, but now there's a failure in the compilation of odcctools: *** Stage: compile (odcctools) [...] gcc -Wall -Wno-import -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1 -D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_ -D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_ -DSTDC_HEADERS -I..//include -I/home/erik/lily/64gub/gubtest/target/darwin-ppc/src/odcctools-20060413/in clude -include /home/erik/lily/64gub/gubtest/target/darwin-ppc/src/odcctools-20060413/incl ude/extern.h -I/home/erik/lily/64gub/gubtest/target/darwin-ppc/src/odcctools-20060413/in clude/foreign -g -O2 -fno-builtin-round -fno-builtin-trunc -c -o writeout.o /home/erik/lily/64gub/gubtest/target/darwin-ppc/src/odcctools-20060413/libs tuff/writeout.c /home/erik/lily/64gub/gubtest/target/darwin-ppc/src/odcctools-20060413/libs tuff/writeout.c: In function ‘writeout’: /home/erik/lily/64gub/gubtest/target/darwin-ppc/src/odcctools-20060413/libs tuff/writeout.c:131: warning: dereferencing type-punned pointer will break strict-aliasing rules /home/erik/lily/64gub/gubtest/target/darwin-ppc/src/odcctools-20060413/libs tuff/writeout.c:264: warning: cast from pointer to integer of different size /home/erik/lily/64gub/gubtest/target/darwin-ppc/src/odcctools-20060413/libs tuff/writeout.c: In function ‘writeout_to_mem’: /home/erik/lily/64gub/gubtest/target/darwin-ppc/src/odcctools-20060413/libs tuff/writeout.c:382: warning: dereferencing type-punned pointer will break strict-aliasing rules /home/erik/lily/64gub/gubtest/target/darwin-ppc/src/odcctools-20060413/libs tuff/writeout.c: In function ‘make_table_of_contents’: /home/erik/lily/64gub/gubtest/target/darwin-ppc/src/odcctools-20060413/libs tuff/writeout.c:1021: error: ‘union anonymous’ has no member named ‘ran_name’ [...] Strangely, this didn't happen when building in 32-bit mode. The problem seems to be that Apple's implementation of ranlib assumes 32-bit architecture for some optimizations, so the lib doesn't work with platforms where sizeof(char*)4. I don't know what to do about this. Is it possible to turn off all mac support in make bootstrap? -- Erik ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond ChangeLog Documentation/user/examples....
Graham Percival wrote:
I'm sure that there's some reason why \tempo x = y is a horrible
construct and must be replaced, but
\context {
\Score
tempoWholesPerMinute = #(ly:make-moment y x)
}
looks unnecessarily complicated. If that's the way it's going to be,
I'll document it, but... why this? Do we want to allow users to have
different tempo in different Staff contexts?
we can hvae something like
#(set-tempo 4 70)
or maybe
tempo = #70
\tempo has to go, because it is strange exception to the general syntax.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Proposed patch: configure version number checking
On Aug 26, 2006, at 11:36 PM, Mats Bengtsson wrote:Please take a look a the mailing list archives for bug-lilypondand lilypond-devel to see what kind of different situations thatthe previous version number checks failed on, before proposingyet another change.Well, what evidence do you have that I didn't do that ? :-)The reason why I believe my patch to be correct is that I'm merely amending the second grep in that pipe to apply criteria consistent with the first grep:• The first grep is looking for [0-9][0-9]*\.[0-9] at the beginning of a line or following a space• The tr transforms both situations into "beginning of a line".• Therefore, adding the beginning of line anchor makes sure that the second grep looks for the same pattern as the first grep. The unpatched version will bite on any word containing a dotted number in the same line that the first grep identified.However, I must admit that upon further review, my patch was not entirely sound in that it would have broken in the case of a tool with a double digit major version number (none of which are currently used in the lilypond build process, but ghostscript may eventually get there), so this would be a bit safer:---diff -ruN lilypond-2.9.16-orig/aclocal.m4 lilypond-2.9.16/aclocal.m4--- lilypond-2.9.16-orig/aclocal.m4 2006-08-26 20:47:16.0 -0700+++ lilypond-2.9.16/aclocal.m4 2006-08-26 21:43:45.0 -0700@@ -34,7 +34,7 @@ ## grab the first version number in --version output. eval _ver=\"\`("$1" --version || "$1" -V) 21 | grep '\(^\| \)[0-9][0-9]*\.[0-9]' \ | head -n 1 \- | tr ' ' '\n' | grep '[0-9]\.[0-9]' | head -n 1 | sed 's/\([0-9.]*\).*/\1/g'\`\"+ | tr ' ' '\n' | grep '^[0-9][0-9]*\.[0-9]' | head -n 1 | sed 's/\([0-9.]*\).*/\1/g'\`\" if test -z "$_ver"; then ## If empty, try date [fontforge]-Either of the two versions of the patch correctly handle two version strings which were broken in the unpatched version:powerpc-apple-darwin8-g++-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5247)guile-1.6-config - Guile version 1.6.7while the second of these is probably quite specific to fink on MacOS X, the first might be quite a bit more common.Matthias___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond ChangeLog Documentation/user/examples....
Han-Wen Nienhuys wrote:
we can hvae something like
#(set-tempo 4 70)
or maybe
tempo = #70
But not
\midi{
tempo = 4. 60
}
?
I'll leave this issue for other people to work out; when it's been
finalized, I'll update the manual. IMO the tempo should be set inside
the \midi{} instead of as a #(...), but I don't know enough about
lilypond internals (numbers, durations, music function arguments, etc)
to give useful suggestions about the exact syntax.
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: changing the midi instrument; broken
On Sun, 27 Aug 2006, Mats Bengtsson wrote:
Some further clarifications below.
...
However, as Erik says below, if you want to store the lyrics into a variable,
you have to do
mylyrics = \lyricmode { Here is my ly -- rics }
and then \lyricsto ... \mylyrics
Still remains the question why at all you would want to store the lyrics
into a variable.
Possible answer: Because you want to reuse the same lyrics at multiple
places in the score.
Greetings,
Juergen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Manual feature-complete
As far as I know, the LilyPond manual is basically ready for a stable release. It is currently missing: - info about the new user-friendly midi tempo. - anything about Joe's page breaking stuff. - anything that gets added to the NEWS file after today. I'm not planning on doing any major work on the manual for the next two or three months; I'm going to concentrate on bug reports. I'll still process doc suggestions, and of course add any other NEWS info before the next stable release. When 2.9.17 comes out, please glance at the docs. If I don't hear any complaints within a week of the web docs being updated, I'll assume that the chapter titles are good and rename the .itely files. This will lose the CVS logs for that chapter, but due to renaming the chapters, some of the filenames are really weird. (Spacing issues = page.itely, Non-musical notation = global.itely, etc -- this sometimes confuses me, and it must be horrible for anybody else trying to edit doc source files) Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: changing the midi instrument; broken
Juergen Reuter wrote:
On Sun, 27 Aug 2006, Mats Bengtsson wrote:
Some further clarifications below.
...
However, as Erik says below, if you want to store the lyrics into a
variable, you have to do
mylyrics = \lyricmode { Here is my ly -- rics }
and then \lyricsto ... \mylyrics
Still remains the question why at all you would want to store the
lyrics into a variable.
Possible answer: Because you want to reuse the same lyrics at multiple
places in the score.
Right! There are often repeated phrases in lyrics.
Also I usually have the notes and words in a separate file from the file
that specifies the part or score.
Paul Scott
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
