El dimecres, 1 de novembre de 2017, a les 11:55:41 CET, Jeroen Ooms va
escriure:
> Several projects use static builds of poppler-cpp to ship standalone
> pdf applications, but since the switch to cmake it is no longer
> possible to build static libs.
>
> Setting -DBUILD_SHARED_LIBS=OFF in cmake
On Wed, Nov 1, 2017 at 3:51 PM, Jason Crain wrote
>
> I don't know how you use poppler in your project, but you may also have
> the option of passing in the path when you construct the GlobalParams
> object.
Hmm that may be the function I am looking for but I don't
On Wed, Nov 01, 2017 at 03:34:36PM +0100, Jeroen Ooms wrote:
> On Wed, Nov 1, 2017 at 3:20 PM, Jason Crain wrote:
>
> > On Mac and Linux the path is hardcoded at compilation time. It's
> > generally in /usr/share/poppler on Linux. Not sure what the standard is
> > on
On Wed, Nov 1, 2017 at 3:20 PM, Jason Crain wrote:
> On Mac and Linux the path is hardcoded at compilation time. It's
> generally in /usr/share/poppler on Linux. Not sure what the standard is
> on Mac. On Windows it looks in \share\poppler relative to the
>
On Wed, Nov 01, 2017 at 02:19:36PM +0100, Jeroen Ooms wrote:
> I maintain the poppler bindings for R which work on Windows, MacOS and
> Linux. However Chineese users on Windows/Mac have reported that
> poppler doesn't find the share data files:
>
> error: Missing language pack for 'Adobe-CNS1'
I maintain the poppler bindings for R which work on Windows, MacOS and
Linux. However Chineese users on Windows/Mac have reported that
poppler doesn't find the share data files:
error: Missing language pack for 'Adobe-CNS1' mapping
Where exactly does poppler look for the 'share' directory? Is
Several projects use static builds of poppler-cpp to ship standalone
pdf applications, but since the switch to cmake it is no longer
possible to build static libs.
Setting -DBUILD_SHARED_LIBS=OFF in cmake only builds a static
libpoppler.a, however libpoppler-cpp still gets built as a dynamic