On Sun, 2014-09-21 at 09:14 +0100, James wrote: > On 21/09/14 08:55, Richard Shann wrote: > > On Sat, 2014-09-20 at 17:27 +0200, Federico Bruni wrote: > >> Thanks Richard, I never used it and I ignored its existence. I'll add > >> that directory to the path in .bashrc. > > In light of the further steps it isn't useful to add that directory to > > the PATH (because the command will not work unless the it is the cwd). > > It is just the web page instructions that need updating to read > > > > cd $LILYPOND_GIT && lily-git.tcl > > > > rather than > >> Type (or copy&paste) into the Terminal: > >> > >> lily-git.tcl > > as at present. > >> It's not worth a new iso update IMO. > > right - the iso seems to be working just fine - with guest extensions > > working out of the box (and that cyrillic thing too). > > BTW my first make failed in the docs - is that expected? > > Richard > > > > > Just to check you did a 'make' before you 'make doc' didn't you?
I haven't tried make doc I just did make I nearly emailed about it at the time and then I realized that I had already made the first (small) mod to the code, adding (chordCompact ,boolean? "Draw chord symbols in a compact fashion?") into define-context-properties.scm and so (as this includes a bit of documentation) I realized that I had blundered by not doing the make at the outset, before starting to modify code, so as to be sure that things were good to start with. I described the problem as being to do with building docs just because of the error message, but I can't reconstruct this (by doing make on the master branch) because lilypond.org is down, so I can't get back to the web page which details the autogen and configure steps needed ... Hence my diffidence about mentioning this in the first place. Once the dust has settled I'll come back to it. Richard > > It will fail then otherwise. > > James _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel