Mark Polesky wrote ./autogen.sh question
Do I need to run ./autogen.sh every time I compile?
No. You only need to rerun it if you need to
configure the make files differently, for example
when you wish to retain the debugging info in the
binary.
Trevor
Hi Carl
I've just applied the patch set to check it out,
probably later today. Looks good so far, apart
from a couple of formatting nitpicks. It's
building now. Back soon.
Trevor
- Original Message -
From: Carl Sorensen c_soren...@byu.edu
To: David Kastrup d...@gnu.org
Cc: Lily
On Thu, Dec 17, 2009 at 10:00:56PM -0800, Mark Polesky wrote:
Do I need to run ./autogen.sh every time I compile?
Intuitively, I would think yes, but the CG is ambiguous:
./autogen.sh is mentioned in 2.1.1 Downloading source code
but not in 2.1.3 Building LilyPond.
No. You need it after you
Carl,
A question. Does your code require autobeaming
rules to be defined for beams of every possible
duration? I ask because the following example beams
inconsistently, and I'm not sure if this is due to your
code or differences in the autobeaming rules for 4/4 and
2/2 time signatures. With
Trevor Daniels t.dani...@treda.co.uk writes:
Carl,
A question. Does your code require autobeaming
rules to be defined for beams of every possible
duration? I ask because the following example beams
inconsistently, and I'm not sure if this is due to your
code or differences in the
On Thu, Dec 17, 2009 at 08:07:08PM -0700, Carl Sorensen wrote:
On 12/17/09 5:55 PM, Graham Percival gra...@percival-music.ca wrote:
My first thought is that I wish we had somebody dedicated to
working on the scheme stuff; I'd love to leave this up to a
trusted person and thereafter
On Fri, Dec 18, 2009 at 11:53:48AM +, Graham Percival wrote:
My preference would be for Notation to have an advert pointing at
Extending... something like Learning 4.6.6, where they show a
rainbow-note example,
(argh, what a painful FAIL with the rainbow example. All those
colors are
Graham Percival wrote Friday, December 18, 2009 12:05 PM
(argh, what a painful FAIL with the rainbow example. All those
colors are defined, but they didn't use all notes in the scale in
the output.)
Could somebody change the last line of the notes to:
g8 fis e d g2 |
and then extend the
On Fri, Dec 18, 2009 at 12:19 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
Graham Percival wrote Friday, December 18, 2009 12:05 PM
Could somebody change the last line of the notes to:
g8 fis e d g2 |
and then extend the high in the lyrics? I can't figure out how
to get a melisma
Trevor Daniels wrote:
Mark Polesky wrote ./autogen.sh question
Do I need to run ./autogen.sh every time I compile?
No. You only need to rerun it if you need to
configure the make files differently, for example
when you wish to retain the debugging info in the
binary.
If I recall
On Fri, Dec 18, 2009 at 1:32 PM, Mats Bengtsson
mats.bengts...@ee.kth.se wrote:
If I recall correctly, you also have to rerun it every time the file VERSION
has been updated, i.e. when a new (minor) version has been released.
No; I believe that Jan responded somewhat angrily when this was last
Graham Percival wrote:
On Fri, Dec 18, 2009 at 1:32 PM, Mats Bengtsson
mats.bengts...@ee.kth.se wrote:
If I recall correctly, you also have to rerun it every time the file VERSION
has been updated, i.e. when a new (minor) version has been released.
No; I believe that Jan responded
Graham Percival wrote Friday, December 18, 2009 12:51 PM
On Fri, Dec 18, 2009 at 12:19 PM, Trevor Daniels
t.dani...@treda.co.uk wrote:
Graham Percival wrote Friday, December 18, 2009 12:05 PM
Could somebody change the last line of the notes to:
g8 fis e d g2 |
and then extend the high in
On 12/18/09 3:58 AM, David Kastrup d...@gnu.org wrote:
Trevor Daniels t.dani...@treda.co.uk writes:
Carl,
A question. Does your code require autobeaming
rules to be defined for beams of every possible
duration? I ask because the following example beams
inconsistently, and I'm not
On 12/18/09 2:49 AM, Trevor Daniels t.dani...@treda.co.uk wrote:
Carl,
A question. Does your code require autobeaming
rules to be defined for beams of every possible
duration? I ask because the following example beams
inconsistently, and I'm not sure if this is due to your
code or
On 12/18/09 4:53 AM, Graham Percival gra...@percival-music.ca wrote:
On Thu, Dec 17, 2009 at 08:07:08PM -0700, Carl Sorensen wrote:
On 12/17/09 5:55 PM, Graham Percival gra...@percival-music.ca wrote:
My first thought is that I wish we had somebody dedicated to
working on the scheme
Carl, you wrote Friday, December 18, 2009 4:21 PM
On 12/18/09 2:49 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
A question. Does your code require autobeaming
rules to be defined for beams of every possible
duration? I ask because the following example beams
inconsistently, and I'm not
If anybody's working on a buildscript and wants a list of lilypond
manuals, here you go:
myDir = os.path.dirname(sys.argv[0])
# use two abspaths to work around some windows python bug
topDir = os.path.join(os.path.abspath(myDir)+os.sep+'..'+os.sep+'..'+os.sep)
topDir = os.path.abspath( topDir )
On 12/18/09 9:52 AM, Trevor Daniels t.dani...@treda.co.uk wrote:
Carl, you wrote Friday, December 18, 2009 4:21 PM
On 12/18/09 2:49 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
A question. Does your code require autobeaming
rules to be defined for beams of every possible
Carl Sorensen c_soren...@byu.edu writes:
On 12/18/09 3:58 AM, David Kastrup d...@gnu.org wrote:
I think that if we establish the rule a broken beam decision is
never reconsidered we can abolish the '* rule for beaming patterns
and instead let a non-specified minimal duration always be broken
On 12/18/09 10:13 AM, David Kastrup d...@gnu.org wrote:
Carl Sorensen c_soren...@byu.edu writes:
On 12/18/09 3:58 AM, David Kastrup d...@gnu.org wrote:
I think that if we establish the rule a broken beam decision is
never reconsidered we can abolish the '* rule for beaming patterns
Carl Sorensen c_soren...@byu.edu writes:
On 12/18/09 9:52 AM, Trevor Daniels t.dani...@treda.co.uk wrote:
Carl, you wrote Friday, December 18, 2009 4:21 PM
On 12/18/09 2:49 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
A question. Does your code require autobeaming
rules to be
Hey everyone.
Without intending the slightest offence towards those of you
who've already put a lot of work into the CG, I think it can
still be clearer. I'm toying around with a bunch of new
paragraphs over here, and I just wanted to let you guys
know, in case one of you is doing some big
23 matches
Mail list logo
