Does anybody feel like working on the out-of-tree documentation build?
That's the current release blocker, but you don't need GUB around to
build it.
mkdir ~/whatever/
cd ~/whatever
/path/to/git/configure --srcdir ~/path/to/git/
make
make doc
then debug. Currently it's not finding
Graham Percival wrote Sunday, September 20, 2009 8:26 PM
I was confused because Joseph keeps on talking about wanting to
copy code from the documentation, and Trevor Daniels recently
said you know what? you guys are nutters. Do whatever you want
with my stuff, now shut up and do work.
...
Trevor Daniels wrote:
For example, we seem to have lost Joseph's really
promising work to document contemporary music.
Not lost. :-) Actually, the delay came at least in part because I was
looking through problems of functionality related to my docs. I'll post
about this on -user.
In message 200909201334.52063.reinh...@kainhofer.com, Reinhold
Kainhofer reinh...@kainhofer.com writes
The LGPLv3 also includes the patents clause and the anti-DRM clause, which
both add additional restrictions, which the GPLv2 does not have.
On the other hand, all lilypond contributors -- by
On Mon, Sep 21, 2009 at 2:34 AM, Carl Sorensen c_soren...@byu.edu wrote:
I think that we shouldn't yet add a tracker for the general solution. We're
still working on the output-suffix issues, which might have a more general
solution.
No problem, as long as you're still patient enough to keep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 21. September 2009 18:49:18 schrieb Anthony W. Youngman:
In message 200909201334.52063.reinh...@kainhofer.com, Reinhold
Kainhofer reinh...@kainhofer.com writes
The LGPLv3 also includes the patents clause and the anti-DRM clause, which
2009/9/20 Michael Käppler xmichae...@web.de:
- your git master compiles without warning and with proper spacing (?,
please proof)
Correct.
I've just done a completely clean build, and it compiles without any
problems (see attached output, which is taken from my local copy of
this page:
Any takers?
:-)
--
Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond - The music typesetter
Avatar®: http://AvatarAcademy.nl| http://lilypond.org
___
lilypond-devel mailing list
lilypond-devel@gnu.org
2009/9/21 Graham Percival gra...@percival-music.ca:
Does anybody feel like working on the out-of-tree documentation build?
That's the current release blocker, but you don't need GUB around to
build it.
I'll give it a go, though I probably won't be much use when it comes
to debugging any build
2009/9/19 Carl Sorensen c_soren...@byu.edu:
Well, during the translation step the translators write output to the output
file using the appropriate output calls, don't they? So they make use of
the file that was created using the output-prefix. So this has *something*
to do with
On 9/21/09 2:38 PM, Neil Puttock n.putt...@gmail.com wrote:
2009/9/19 Carl Sorensen c_soren...@byu.edu:
Well, during the translation step the translators write output to the output
file using the appropriate output calls, don't they? So they make use of
the file that was created using
On Mon, Sep 21, 2009 at 1:48 PM, Carl Sorensen c_soren...@byu.edu wrote:
On 9/21/09 2:38 PM, Neil Puttock n.putt...@gmail.com wrote:
2009/9/19 Carl Sorensen c_soren...@byu.edu:
Well, during the translation step the translators write output to the output
file using the appropriate output
2009/9/19 Ian Hulin i...@hulin.org.uk:
Hi Carl, Neil,
I'm quite happy to re-think the proposal if what I have in mind contravenes
existing design architecture.
Put it down to relative inexperience and the fact I don't get opportunity to
work on lilly as often as I'd like.
Anyhow, here are
On Fri, 2009-09-18 at 18:06 -0600, Carl Sorensen wrote:
It would be convenient if the output-prefix could be defined in the /score
or /layout block that causes the creation of a Score context. I think
that's why Ian was wanting to make it a context property of Score. But I
suspect (although
Hi everybody,
Recently I've been getting loads of error messages when building the
docs; they all relate to Texinfo macros which don't have arguments.
Here's a random example:
out-www//notation/repeats.texi:879: warning: @snippets defined with 0
arguments should be invoked with {}
I had a look
Hi Joe,
Joe Neeman wrote:
On Fri, 2009-09-18 at 18:06 -0600, Carl Sorensen wrote:
It would be convenient if the output-prefix could be defined in the /score
or /layout block that causes the creation of a Score context. I think
that's why Ian was wanting to make it a context property of
2009/9/21 Graham Percival gra...@percival-music.ca:
Currently it's not finding version.itexi in
Documentation/out-www/ ... it gets built in Documentation/out/.
Running as root, I've got version.itexi in both Doc*/out-www and
Doc*/out, but the build fails when processing out-www/general.texi:
Hi,
Here's a little patch which allows the use of direction tokens with
manual beaming:
http://codereview.appspot.com/120060/show
Please review.
Thanks,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Neil Puttock wrote Monday, September 21, 2009 10:23 PM
Recently I've been getting loads of error messages when building
the
docs; they all relate to Texinfo macros which don't have
arguments.
Has the version of texinfo you are using changed? I use texi2html,
admittedly a very old version,
On Sun, 20 Sep 2009, Graham Percival wrote:
Now, at some point, there will be some important bug fix or new
feature in guile 1.9, which is only published under v3. *Then* we'd
have problems... but wait! If guile is truly under LGPL, and not
GPL, then there should be no problems. I mean, if you
Le lundi 21 septembre 2009 à 23:54 +0100, Trevor Daniels a écrit :
Has the version of texinfo you are using changed? I use texi2html,
admittedly a very old version, for my local doc compiles and don't
see this problem.
Remember that the accepted Texinfo language depends on the Texinfo
lgtm
http://codereview.appspot.com/120060
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Le lundi 21 septembre 2009 à 09:12 +0100, Graham Percival a écrit :
then debug. Currently it's not finding version.itexi in
Documentation/out-www/ ... it gets built in Documentation/out/.
I couldn't reproduce this error, but I hit a truckload of broken image
paths, and hopefully fixed them.
On 9/21/09 4:32 PM, Neil Puttock n.putt...@gmail.com wrote:
Hi,
Here's a little patch which allows the use of direction tokens with
manual beaming:
http://codereview.appspot.com/120060/show
LGTM.
Carl
___
lilypond-devel mailing list
24 matches
Mail list logo
