[MacPorts] #57875: port:poppler shouldn't require C++14?!

MacPorts noreply at macports.org
Wed Jan 9 12:51:11 UTC 2019

#57875: port:poppler shouldn't require C++14?!
  Reporter:  RJVB     |      Owner:  dbevans
      Type:  defect   |     Status:  assigned
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:
Resolution:           |   Keywords:
      Port:  poppler  |

Comment (by RJVB):

 Sounds like they should release a poppler2 or poppler-ng ... or we could
 do something like that ourselves (where the newer versions either get a
 suffix if the build system allows, or are installed to $prefix/libexec).

 >  Upstream didn't seem to point out the reason for C++14 source in the

 Well, the changelog does, though not why they decided to use
 std::make_unique . A version diff should show if that change simplified
 the code.

 BTW, I now understand why my build with -std=c++11 succeeded, it must have
 been overridden by CMake:


 Anyway, I was happily using 0.68.0 until yesterday (= the least release
 without C++14), and only upgraded because that version crashed on a
 particular PDF (though only on Linux...). IOW, could be a good branch
 point for something like poppler-ng, or a pegged "poppler-og" port. Not
 really certain what's wisdom here but I sure know that I hate having to
 rebuild dependents just because some utility library broke ABI - again.

Ticket URL: <https://trac.macports.org/ticket/57875#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS

More information about the macports-tickets mailing list