On a related note I was unable to build a recent checkout of Poppler because it tries to build all the GTK based tests regardless of whether or not the configure script found gdk/gtk etc.
I got around it by commenting out the 'tests' target in Makefile (I was in a hurry), after that it builds & runs fine on Debian Lenny. On 9 March 2011 12:12, Tim Brody <[email protected]> wrote: > $ git clone git://git.freedesktop.org/git/poppler/poppler > $ cd poppler > $ ./autogen.sh --prefix=/usr/local/poppler --disable-cairo-output > --disable-poppler-glib --disable-gtk-test --disable-poppler-qt4 > --disable-splash-output --disable-poppler-cpp > $ make > > ... > Building poppler with support for: > font configuration: fontconfig > splash output: no > cairo output: no > abiword output: no > qt4 wrapper: no > glib wrapper: no > introspection: no > cpp wrapper: no > use gtk-doc: no > use libjpeg: yes > use libpng: yes > use libtiff: no > use zlib: no > use libcurl: no > use libopenjpeg: yes > use cms: yes > command line utils: yes > > $ make 2>&1 > > ... > gtk-test.cc:14:21: error: gdk/gdk.h: No such file or directory > In file included from gtk-test.cc:19: > ../glib/poppler.h:22:25: error: glib-object.h: No such file or directory > In file included from ../glib/poppler.h:201, > from gtk-test.cc:19: > > (Followed by more errors related to cairo) > > I'd like to "backport" current poppler onto servers and even with distros > <year old (Fedora Core 13) it's a nightmare. Is it unreasonable to ask > poppler to maintain compatibility with stable releases of dependent > libraries e.g. cairo 1.0, glib 2.0 etc? It surely can't help testing to > restrict your community to those people on the very latest library levels? > > -- > All the best, > Tim. > _______________________________________________ > poppler mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/poppler >
_______________________________________________ poppler mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/poppler
