Op maandag 05-07-2010 om 03:51 uur [tijdzone +0200], schreef Reinhold
Kainhofer:
> > Apparently the newly added lilypond-book directory does something
> > stupid, builds without using a target or something.
>
> Not that I can see.
Stupid is not the right word, silly is probably better :-)
Turns
Hi Carl
Download and applied to current git, but make fails:
make[1]: *** No rule to make target `include/beam-settings.hh',
needed by `out/beaming-pattern.o'. Stop.
make[1]: Leaving directory `/media/lilypond-git/lily'
make: *** [all] Error 2
Does this need to be applied over your previous
We had three people working on build stuff this morning, and in the
mix I decided to use different version numbers when adding \version
"2.12.0" to files. release/unstable is a mess.
Could somebody make release/unstable be exactly the same as master? I
don't care if you delete it and make a new
Graham Percival writes:
> We had three people working on build stuff this morning, and in the
> mix I decided to use different version numbers when adding \version
> "2.12.0" to files. release/unstable is a mess.
>
> Could somebody make release/unstable be exactly the same as master? I
> don't
Apply on top of current git. But remember to do
make bin-clean
or
rm lily/out/*
before doing make. I've removed some c++ files, and so the old binaries
have to go.
Also, I've left some debug statements commented out in
scm/auto-beam.scm. They'll be removed before pushing, but I got tired
o
On Mon, Jul 5, 2010 at 12:37 PM, David Kastrup wrote:
> Graham Percival writes:
>
>> Could somebody make release/unstable be exactly the same as master? I
>> don't care if you delete it and make a new one, or do some fancy git
>> thing to move the ref around, or what... I just want to get rid of
On 2010/07/05 05:48:16, MikeSol wrote:
I see 3.5 places where the patch may need improvement. 1 is that
lineto and
curveto seem unnecessary, as they can be automatically detected by the
number of
function arguments.
For purposes of human readability, I think we should keep lineto and
curv
Am Montag, 5. Juli 2010, 14:10:23 schrieb Graham Percival:
> On Mon, Jul 5, 2010 at 12:37 PM, David Kastrup wrote:
> > There are basically two ways to do that. One is more or less a relabel
> > and would consequentially lose history.
>
> If it loses history from release/unstable, I consider that
I'm trying to build the documentation to make sure it works with my new
autobeam code.
When I do make doc-clean && make doc, I get the following error:
cd ./out-www; texi2pdf -I /Users/Carl/lilypond/Documentation -I
/Users/Carl/lilypond/input/regression/abc2ly --batch collated-files.texi
This is
Graham Percival writes:
>> There are basically two ways to do that. One is more or less a relabel
>> and would consequentially lose history.
>
> If it loses history from release/unstable, I consider that a desirable
> side effect.
>
>> The other is a trivial merge
>> with master with a merge st
On Mon, Jul 5, 2010 at 1:26 PM, Carl Sorensen wrote:
> make[4]: *** No rule to make target `""', needed by
> `out-www/collated-files.tely'. Stop.
> make[3]: *** [WWW-1] Error 2
> rm out-www/collated-files.pdf.omf out-www/weblinks.itexi
> make[2]: *** [WWW-1] Error 2
> make[1]: *** [WWW-1] Error 2
On 7/5/10 7:22 AM, "Graham Percival" wrote:
> On Mon, Jul 5, 2010 at 1:26 PM, Carl Sorensen wrote:
>> make[4]: *** No rule to make target `""', needed by
>> `out-www/collated-files.tely'. Stop.
>> make[3]: *** [WWW-1] Error 2
>> rm out-www/collated-files.pdf.omf out-www/weblinks.itexi
>> mak
On Mon, Jul 05, 2010 at 07:47:05AM -0600, Carl Sorensen wrote:
>
> On 7/5/10 7:22 AM, "Graham Percival" wrote:
>
> > It's to do with the lilypond-book regression test build stuff,
> > although I didn't realize it affected the normal doc build.
>
> Any way to work around it?
Sorry, I don't know
Am Montag, 5. Juli 2010, 15:22:15 schrieb Graham Percival:
> On Mon, Jul 5, 2010 at 1:26 PM, Carl Sorensen wrote:
> > make[4]: *** No rule to make target `""', needed by
> > `out-www/collated-files.tely'. Stop.
> > make[3]: *** [WWW-1] Error 2
> > rm out-www/collated-files.pdf.omf out-www/weblink
On Mon, Jul 5, 2010 at 3:40 PM, Reinhold Kainhofer
wrote:
>> It's to do with the lilypond-book regression test build stuff,
>> although I didn't realize it affected the normal doc build.
>
> The problem was that Jan renamed the variable that collects the output files,
> but didn't change the GNUma
All the source files in this dir should appear in the dist tarball. I
tried a quick fix since it only complained about one file, but then it
complained about 8 more, so I'm guessing that none of these files are
included.
The simplest way to check is to do "make dist", then look inside the
tarball
Removed four instances of double periods.
--
Michael
>From d113bf5029d581b105fa8d764a51fe14db61368b Mon Sep 17 00:00:00 2001
From: Mikemoral
Date: Mon, 5 Jul 2010 12:55:53 -0700
Subject: [PATCH 2/2] Remove double periods in glossary
Removed 4 instances of double periods.
---
Documentation/music
Carl, you wrote Monday, July 05, 2010 12:39 PM
Apply on top of current git. But remember to do
make bin-clean
or
rm lily/out/*
before doing make. I've removed some c++ files, and so the old
binaries
have to go.
Of course! I should have remembered from the last time.
Thanks for your
"Michael" wrote Monday, July 05, 2010
8:58 PM
Removed four instances of double periods.
Pushed to git; thanks!
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Am Montag, 5. Juli 2010, um 20:51:26 schrieb Graham Percival:
> All the source files in this dir should appear in the dist tarball. I
> tried a quick fix since it only complained about one file, but then it
> complained about 8 more, so I'm guessing that none of these files are
> included.
[...]
>
Carl, you wrote Monday, July 05, 2010 1:26 PM
I'm trying to build the documentation to make sure it works with
my new
autobeam code.
When I do make doc-clean && make doc, I get the following error:
[snip error messages]
I get the same error. However, I did build the docs
successfully on
On 7/5/10 5:39 PM, "Trevor Daniels" wrote:
>
>
> Carl, you wrote Monday, July 05, 2010 1:26 PM
>
>
>> I'm trying to build the documentation to make sure it works with
>> my new
>> autobeam code.
>>
>> When I do make doc-clean && make doc, I get the following error:
>
> [snip error messages]
Am Dienstag, 6. Juli 2010, um 01:39:50 schrieb Trevor Daniels:
> Carl, you wrote Monday, July 05, 2010 1:26 PM
>
> > I'm trying to build the documentation to make sure it works with
> > my new
> > autobeam code.
>
> > When I do make doc-clean && make doc, I get the following error:
> [snip error
Am Montag, 5. Juli 2010, um 14:10:23 schrieb Graham Percival:
> On Mon, Jul 5, 2010 at 12:37 PM, David Kastrup wrote:
> > Graham Percival writes:
> >> Could somebody make release/unstable be exactly the same as master? I
> >> don't care if you delete it and make a new one, or do some fancy git
>
Am Dienstag, 6. Juli 2010, um 01:33:16 schrieb Reinhold Kainhofer:
> Am Montag, 5. Juli 2010, um 20:51:26 schrieb Graham Percival:
> > All the source files in this dir should appear in the dist tarball. I
> > tried a quick fix since it only complained about one file, but then it
> > complained abo
Added German name from "alla breve" and create consistency for "cut
time."
--
Michael
>From db8f11d1f8cfaaaccdf6c921a014378071fac29f Mon Sep 17 00:00:00 2001
From: Mikemoral
Date: Mon, 5 Jul 2010 19:04:17 -0700
Subject: [PATCH 2/2] Edits to glossary
Added German name from "alla breve" and creat
OK, I've loaded patch set 2. This patch set makes a clean doc build.
To make this patch work, you'll need to do the following:
1) Apply the patch
2) Clean out the old binaries:
make bin-clean or rm lily/out/*
3) Update the snippets in Documentation/snippets from
Documentation/snippets/new
27 matches
Mail list logo
