evince-3.36.3

[Bruce Dubbs]

New point release.

[Douglas R. Reno]

News
====

Fix Evince on MacOS

backends:
  *  Annotate functions that wraps formatting strings (#1410, Germán Poo-Caamaño)
  *  Fix -Wformat-zero-length warning (Germán Poo-Caamaño)

build:
  *  use so suffix on macOS (Tom Schoonjans)

ci:
  *  Fix meson targets (Germán Poo-Caamaño)

cut-n-paste:
  *  Annotate functions that wraps formatting strings (#1410, Germán Poo-Caamaño)

Developers:
  * Germán Poo-Caamaño, Tom Schoonjans

[Douglas R. Reno]

3.36.2:

================
Evince    3.36.2
================

shell:
  *  check type of window/sidebar objects (#1409, Ilario Gelmetti)

build:
  *  Use lowercase for project name in meson (Germán Poo-Caamaño)

ci:
  *  build with meson by default and autotools manually (Germán Poo-Caamaño)

flatpak: Update Poppler to 0.88.0 (Casey Jao)

Developers:
  * Casey Jao, Germán Poo-Caamaño, Ilario Gelmetti

Translations:
  * sicklylife (Japanese)

[Douglas R. Reno]

Something interesting has happened with this version of evince.

It seems that the autotools files weren't generated/shipped (which wouldn't be a problem, but autogen.sh fails!)

autoreconf: running: aclocal --force -I m4 ${ACLOCAL_FLAGS}
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
autoreconf: running: /usr/bin/autoconf --force
configure.ac:78: error: possibly undefined macro: AM_GNU_GETTEXT_VERSION
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:82: error: possibly undefined macro: AM_GNU_GETTEXT
autoreconf: /usr/bin/autoconf failed with exit status: 1

I have looked and there is a meson port available, however it seems to still be quite buggy. Most of the commits in 3.36.2 and 3.36.3 were for meson.

Should we port over to meson? I'll note that it's bad practice to remove autotools support in a point release. I'll also need to build Texlive to check on the CFLAGS before configure.

The other option would be to try to fix the autotools problems here. Another would be to file a bug report upstream and hold for another release (which isn't the optimal option in my opinion).

I'm leaning towards converting to meson in this case. I can build Texlive tomorrow. Opinions please?

[Bruce Dubbs]

I'd say go ahead and try with meson. I don't have all the dependencies but so far this worked for me:

mkdir build &&
cd    build &&

meson --prefix=/usr -Dnautilus=false -Dsystemduserunitdir=no.. &&
ninja &&
ninja install

Actually install takes a few seconds.

I only did a quick test with one pdf file.

[Douglas R. Reno]

For reference, the install takes a few seconds because it generates the gtk-doc documentation at install time unless gtk-doc is disabled. Note that this also would make gtk-doc a required dependency unless we add -Dgtk_doc=false (which I plan to do)

[Douglas R. Reno]

Also, after installing Texlive today, I can confirm that the CFLAGS/CXXFLAGS/LDFLAGS can go too :)

[Douglas R. Reno]

Fixed at r23235

[Bruce Dubbs]

Milestone renamed

[Bruce Dubbs]

Milestone renamed