Hi Even,
Thanks for the clarification. In that case I don't need to build it as a
plugin, since this build will only end up on my own local machine.
Andreas
On 2019-11-20 11:08, Even Rouault wrote:
Andreas,
I wonder what exactly the build option "--enable-pdf-plugin enable PDF
driver as a plugin (included in libgdal by default)" means?
Plugin here means as a separate .so/.dll : gdal_PDF.so/dll
Mostly for licensing concerns if using the Poppler backend since Poppler is
subject to the GPL. So you can make a libgdal build mostly subject to X/MIT or
similar licenses, and in case you need it, use a gdal_PDF plugin subject to
GPL
How does this relate to the other options of building against
poppler/podofo/pdfium ?
It is orthogonal to the poppler/podofo/pdfium backend(s) used.
For the pdfium backend, which is a bit involved to build (pdfium actually),
there were also issues with symbol clashes between embedded libraries in
pdfium and others used by GDAL, and making a plugin instead of linking in core
GDAL library seemed to "solve" (workaround) issues. Was at least true on Linux
with pdfium of a few years ago. I don't remember having had such issues with
the recent upgrade I did in GDAL master.
Even
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
