Thanks for the offer. I have moved to a slackware 14 base in which poppler is detected. Running into other problems though which i will start a new question about.
Jay
On Fri, Nov 9, 2012 at 9:12 PM, Fat-Zer fatzer2@gmail.com wrote:
2012/11/4 Jay jayflood@gmail.com:
Sorry Darrell yes it was David.
My configure options look the same as yours (apart from GCC INVISIBILITY) and the patch history is reflected in my latest git pull. The patch from Fat_Zer simply makes the poppler check regardless if you are building
KPDF
or not. It looks like my poppler is not being found.
We will be moving to a slackware 14 base shortly so i will be recompiling everything again shortly. Would have been nice to know why my poppler is
not
being found though.
Cmake does nothing more when runs pkg-config to set it's internal variable... If pkg-config returns wrong data it's a system problem. If cmake variables are setted properly in it's cache (are they?) it's supposed to be a trinity bug. If variables are not setted correctly... I don't know... It's magic...or some sort of complicated upstream cmake bug etc...
You can find additional info why HAVE_POPPLER_{16,20} checks are failed in the CMakeFiles/CMakeError.log in the build director... If you are still intrested in solving the problem can you upload/post content of your build directory after configuration, your full configure/build log (with VERNOSE=1) and your cmake configuration command...
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@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