|
From: | Aymeric O. |
Subject: | Re: Building documentation: bad PNG output |
Date: | Sat, 28 Jun 2014 17:59:16 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
I found where the problem is! In make/lilypond-vars.make, the options used by LilyPond to generate the output files are given there: ## override from cmd line to speed up. ANTI_ALIAS_FACTOR=2 LILYPOND_JOBS=$(if $(CPU_COUNT),-djob-count=$(CPU_COUNT),) LANG_TEXIDOC_FLAGS:=$(foreach lang,$(LANGS),--header=texidoc$(lang)) LANG_DOCTITLE_FLAGS:=$(foreach lang,$(LANGS),--header=doctitle$(lang)) LILYPOND_BOOK_LILYPOND_FLAGS=-dbackend=eps \ --formats=ps,png,pdf \ $(LILYPOND_JOBS) \ -dinclude-eps-fonts \ -dgs-load-fonts \ --header=doctitle \ $(LANG_DOCTITLE_FLAGS) \ --header=texidoc \ $(LANG_TEXIDOC_FLAGS) \ -dcheck-internal-types \ -ddump-signatures \ -danti-alias-factor=$(ANTI_ALIAS_FACTOR) And the problem comes from "-danti-alias-factor=$(ANTI_ALIAS_FACTOR)" (=2), which is responsible for the crushed PNG files. I tested it on my own scores, and it gives the same result. So it looks like the /usr/bin/lilypond I built can’t handle "-danti-alias-factor>=2", but why? I tried this option whith the precompiled version of LilyPond, and I get the same PNG files, so it must be a system-wide problem, as it was suggested before. I’m using Zenwalk GNU/Linux, a Slackware-based system. On 06/27/2014 02:47 PM, James wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |