I think it would be even better to just replace current USE_EVINCE usage with something like USE_PDFVIEW (keeping the original defines for fixing differences), but that seems like a pretty troublesome adventure to start now that the current usage is so ingrained in the codebase.
I think putting in 'or defined USE_ATRIL' into every USE_EVINCE check is about the same burden in terms of workload (and if you mess up, the bugs may or may not become apparent at first for whatever weird gcc reason, though I'm quite unsure about that – is there any actual behavioral difference between the two libs that required #ifdef-ing behavior instead of just conditionally defining functions as NOP if no PDF viewer was found?). sj Ekkor: 2025. december 1. 22:36:50 CET, Andreas Schneider <[email protected]> írta: >Wouldn't it be more straight forward to test for USE_EVINCE or USE_ATRIL in >the sources? > >Andreas > >Am 1. Dezember 2025 16:26:18 MEZ schrieb Richard Shann ><[email protected]>: >>With the current version of configure.ac the Print View is no longer >>present if you are building against atril. I have to use >>/configure CFLAGS="-DUSE_EVINCE" >>to get a typeset. >>There are a lot of places in the sources where USE_EVINCE is tested >>with the understanding that it means that either Evince or Atril is >>available. Can the configure.ac be changed to ensure USE_EVINCE is >>always true if USE_ATRIL is? >> >>Richard >> >> >
