[poppler] ABI stability
Heinz Wiesinger
HMWiesinger at liwjatan.at
Thu May 24 19:03:56 UTC 2018
On Thursday, 24 May 2018 20:33:40 CEST Adam Reichold wrote:
> Hello Heinz,
>
> Am 24.05.2018 um 20:13 schrieb Heinz Wiesinger:
> > Of course, there's also the possibility that I'm missing something, in
> > which case, mea culpa. However, I would still appreciate some explanation
> > in that case, if only for my personal curiosity :)
>
> libpoppler is not considered a public API. The frontend libraries
> (libpoppler-{qt5,glib,cpp}) are and therefore have API and ABI stability
> guarantees. Applications should try to target those and avoid working
> directly against Poppler's internal interfaces as much as possible. If
> the frontend libraries miss any specific functionality, people will
> usually try to expose that in a way that is idiomatic for the frontend
> in question.
Right, so the idea is that applications link the frontend libraries only.
Since those are updated with poppler, applications shouldn't be affected by
the so-version bump of libpoppler. I'll have a closer look what's happening
here then. Thanks for the info! :)
Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.freedesktop.org/archives/poppler/attachments/20180524/73747e80/attachment.sig>
More information about the poppler
mailing list