On Wed, Nov 01, 2017 at 03:34:36PM +0100, Jeroen Ooms wrote: > On Wed, Nov 1, 2017 at 3:20 PM, Jason Crain <ja...@inspiresomeone.us> 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 > > installation directory. > > OK that is unfortunate. Would it be possible to introduce an option to > set this path dynamically at runtime; e.g via an environment variable > or via an api call? > > In our case we statically link libpoppler with the R bindings on > MacOS/Windows. This works very well for users, but there isn't a fixed > installation directory; it depends on where the user installs the R > package. So it would be really nice if there is a way to point > libpoppler to the correct path when the R package gets loaded, rather > than hardcoding this at build-time. >
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. _______________________________________________ poppler mailing list poppler@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/poppler
