17 Aug
2012
17 Aug
'12
8:21 p.m.
On 17 August 2012 16:19, Darrell Anderson <humanreadable(a)yahoo.com> wrote:
I would say instead file a bug report requesting that we port to
poppler. That's what everyone else uses (and has for quite some time)
and is designed specifically as a library instead of including xpdf
It's
definitely building xpdf from the GIT tree. We need to
apply all patches or pull the latest xpdf code. Note the numerous deprecation
warnings associated with xpdf as well:
The primary issue then would seem to be that the internal Trinity xpdf is not being
updated with security patches.
The CMake files could probably be changed to use
xpdf
libraries instead of the statically built xpdf libraries from the GIT tree. Well
above my coding grade.
Likewise.
I'll write Yet Another Bug Report. Or two.
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting