bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Regtest compiling


From: Graham Percival
Subject: Re: Regtest compiling
Date: Tue, 30 Nov 2010 06:47:52 +0000
User-agent: Mutt/1.5.20 (2009-06-14)

On Tue, Nov 30, 2010 at 07:34:04AM +0100, James Bailey wrote:
> 
> 1. Is there any reason I should install this if I can already compile 
> lilypond on my computer without lilybuntu?

If you can already compile lilypond, and are confident that it's
compiling correctly, you have no weird ghostscript or font issues,
that you've installed your compiled version in the PATH so typing
"lilypond" doesn't accidentally call the wrong version, etc etc --
then no, there's no reason to install lilybuntu.

I was suggesting lilybuntu because it gives you a trusted platform
where everything works (well, works sufficiently well).  There is
a non-zero chance that you might encounter problems, not from the
regtests, but just because of your development environment.

In light of the rest of your email, this "non-zero chance" is only
very slightly non-zero, so go ahead and use your current setup...
but I don't regret suggesting lilybuntu, for the sake of the email
archives if nothing else.

> 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.

Sorry, I don't understand this?  Typing "make test" will compile
the regtests; I thought that was what you wanted?

> Maybe there needs to be a separate section in the CG on that occasional task 
> of manually compiling all of the regtests?

...
I don't think anybody should be manually compiling regtests, but
you could do something like:

cd input/regression/
for f in *.ly; do lilypond $f; done;

Note that in this case, you don't even need to compile lilypond
itself.  All you need is the git repository, and a normal GUB
lilypond.

> 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.

Why remove any lines?  The compiled version of the regtests have
something added, but the version in git can be easily compiled on
the command-line.

I'm not familiar with the specific problem you're trying to find,
so I can't speak to that.

Cheers,
- Graham



reply via email to

[Prev in Thread] Current Thread [Next in Thread]