[poppler] poppler-0.12.1 vs poppler-0.12.(2|3) ABI (and API) breakage?

Rex Dieter rdieter at math.unl.edu
Fri Jan 15 09:18:18 PST 2010


Pino Toscano wrote:

> Hi,
> 
> Alle venerdì 15 gennaio 2010, Rex Dieter ha scritto:
>> Noticed that after upgrading to 0.12.2 (and subsequently 0.12.3), that
>> inkscape-0.47 (built against 0.12.1) no longer import pdfs, and would
>> bail with:
>> 
>> inkscape: symbol lookup error: inkscape: undefined symbol:
>> _ZN13GfxColorSpace5parseEP6Object
>> 
>> and confirmed that rebuilding inkscape-0.47 now fails.
>> 
>> Was this an intentional change?
>> Is this is poppler or inkscape (or both) issue/bug ?
> 
> The poppler core library is considered private and with no API/ABI
> stability guarantees of any kind (that's why you have to force the
> autotools/cmake buildsystems to install the private xpdf headers); the
> inkscape developers know their PDF filter is using private API, although a
> solution is not being worked on (yet?).

OK, from reading some related historical threads, I came to the same 
conclusion... the -glib and -qt bindings have recommended/public api/abi.

-- Rex

-- Rex




More information about the poppler mailing list