[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Regtest compiling
From: |
James Bailey |
Subject: |
Regtest compiling |
Date: |
Tue, 30 Nov 2010 07:34:04 +0100 |
On Nov 30, 2010, at 6:07 AM, Graham Percival wrote:
> On Mon, Nov 29, 2010 at 06:26:04PM +0100, James Bailey wrote:
>> If anyone has any tips on how to compile them easily, I'd be
>> more than willing to listen.
>
> 1. install lilybuntu. Link+explanations in the CG.
> 2. compile lilypond. CG 3.
> 3. do CG 8.5 Compiling regression tests.
>
> I'm not absolutely confident about the quality of the docs in the
> latter two steps (I just haven't checked them recently), so if you
> get confused (if you spend more than 10 minutes on a single step),
> email again and we'll discuss it (and I'll clarify the CG as
> needed).
>
> Cheers,
> - Graham
1. Is there any reason I should install this if I can already compile lilypond
on my computer without lilybuntu?
2. done
3. How do tracking memory usage and source code changes get me any closer to
easily compiling the regtests? I'm guessing they probably don't.
Maybe there needs to be a separate section in the CG on that occasional task of
manually compiling all of the regtests?
Basically, I want a way to have access to the regression tests so without the
header declaration at the top so that I can easily run lilypond on them. I'm
sure, since I can compile the documentation, whatever is used to generate the
regression tests is there somewhere, but since I am a noob, I do things the
only way I know how. which is to copy all of the *.ly files into a folder,
remove the first couple of lines from all of them, and run lilypond on them.
Some of the regtests aren't designed to show something that can be seen in the
html or pdf documentation. Some of them only show errors when you actually
compile them and create a single pdf for the regtest. That's what I've been
trying to find an easy way of doing.
I'm trying to find easier ways of catching things like this:
http://www.mail-archive.com/address@hidden/msg16128.html