On Sun, 2025-09-28 at 20:40 +0200, sj wrote:
> Thanks, I managed to patch out too many things, now I understand
> better. 
> Fixed patch for Andreas (maybe):
> 
> --- a/configure.ac      2025-09-28 13:05:57535618217 +0200
> +++ b/configure.ac      2025-09-28 13:10:51364641998 +0200
> @@ -275,7 +275,7 @@
>       fi
> 
>       if test "x$have_evince2_32" = "xno"; then
> -      PKG_CHECK_MODULES(ATRIL, atril-view-1.5.0 >= 1.5
> have_atril=yes, 
> have_atril=no)
> +      PKG_CHECK_MODULES(ATRIL, atril-view-1.5.0 >= 1.5,
> have_atril=yes, 
> have_atril=no)
>         CFLAGS="$CFLAGS $ATRIL_CFLAGS"
>         LIBS="$LIBS $ATRIL_LIBS"
>       fi
> --- a/src/scripting/scheme-callbacks.c  2025-09-07 14:13:44.000000000
> +0200
> +++ b/src/scripting/scheme-callbacks.c  2025-09-28 16:01:53.998036258
> +0200
> @@ -38,5 +38,6 @@
>   #include "printview/printview.h"
>   #include "printview/markupview.h"
>   #include "display/calculatepositions.h"
> +#include "display/displayanimation.h"
>   #include "source/source.h"
>   #include "source/sourceaudio.h"

Thanks.
I've committed the first hunk to the repository (although Savannah is
being very slow to update), the second one went in a fortnight ago (I
think in connection with flatpak).

> 
> I now just get red text that says "INVALID! try Score->Check Score 
> command...", I did so and it said no problem, but console spits out
> some 
> pretty weird error messages stating that "Denemo - WARNING : Trying
> to 
> read the pdf file file:///tmp/Denemo_FZSBD3/denemoprintA.pdf gave an 
> error: File type PDF document (application/pdf) is not supported". 
> Checked the file in /tmp, it's valid PDF as far as I (and Zathura)
> can 
> see, so Lilypond rendering is probably fine. Have you seen this
> before? 

so this will be the evince library not being configured to cope with
PDF, switching to atril should be good.

Richard

> (This is not new at all, the same as when I've given up on fixing
> Denemo 
> on my machine the first time a few months ago, so probably not a
> recent 
> commit, might have even been just a broken dependency update.)
> 
> 


Reply via email to