Re: [Inkscape-devel] pdf-input.cpp:544: error: '_preview_output_dev' was not declared in this scope
Jon A. Cruz wrote:
On Oct 20, 2007, at 6:49 PM, Joshua Facemyer / Impressus Art wrote:
Okay, will the same pdf functionality be present then? (Also, is this a workaround to get the thing compiling at a loss of functionality, or is it something that should / will be addressed in a future update to make it compile in an environment that it should without difficulty?)
Someone familiar with the specifics would have to look into it, but I think it's a work-around in losing a bit of functionality...
But from what I recall, it's probably due to us using internals of poppler that are not part of the public API. Get and build poppler yourself and you might have the needed .h, but use standard packing and you probably won't.
Part of me only seeing this recently was that only recently had I gotten a new enough poppler in macports.
I use Gentoo, so my poppler should be "my own" build. Same with Jeff. (Had you figured this out yet, Jeff?)
Is it maybe that some switch needs to be passed to poppler when building it?
JF
On Sun, 21 Oct 2007 11:13:31 -0500, Joshua Facemyer / Impressus Art wrote:
Jon A. Cruz wrote:
On Oct 20, 2007, at 6:49 PM, Joshua Facemyer / Impressus Art wrote:
Okay, will the same pdf functionality be present then? (Also, is this a workaround to get the thing compiling at a loss of functionality, or is it something that should / will be addressed in a future update to make it compile in an environment that it should without difficulty?)
Someone familiar with the specifics would have to look into it, but I think it's a work-around in losing a bit of functionality...
But from what I recall, it's probably due to us using internals of poppler that are not part of the public API. Get and build poppler yourself and you might have the needed .h, but use standard packing and you probably won't.
Part of me only seeing this recently was that only recently had I gotten a new enough poppler in macports.
I use Gentoo, so my poppler should be "my own" build. Same with Jeff. (Had you figured this out yet, Jeff?)
Is it maybe that some switch needs to be passed to poppler when building it?
Here's the current poppler package header files. If there is a missing or non-public .h, and a poppler --configure option will force it to be installed, I'll file the gentoo bug to request that as a poppler USE variable.
# emerge poppler -pv ; equery files poppler | grep \.h
These are the packages that would be merged, in order:
Calculating dependencies ..... ..... ........ done! [ebuild R ] app-text/poppler-0.6.1 USE="jpeg zlib -cjk" 0 kB
Total: 1 package (1 reinstall), Size of downloads: 0 kB /usr/include/poppler/Annot.h /usr/include/poppler/Array.h /usr/include/poppler/BaseFile.h /usr/include/poppler/BuiltinFont.h /usr/include/poppler/BuiltinFontTables.h /usr/include/poppler/CMap.h /usr/include/poppler/Catalog.h /usr/include/poppler/CharCodeToUnicode.h /usr/include/poppler/CharTypes.h /usr/include/poppler/CompactFontTables.h /usr/include/poppler/Decrypt.h /usr/include/poppler/Dict.h /usr/include/poppler/Error.h /usr/include/poppler/ErrorCodes.h /usr/include/poppler/FontEncodingTables.h /usr/include/poppler/FontInfo.h /usr/include/poppler/Form.h /usr/include/poppler/Function.h /usr/include/poppler/Gfx.h /usr/include/poppler/GfxFont.h /usr/include/poppler/GfxState.h /usr/include/poppler/GlobalParams.h /usr/include/poppler/JArithmeticDecoder.h /usr/include/poppler/JBIG2Stream.h /usr/include/poppler/JPXStream.h /usr/include/poppler/Lexer.h /usr/include/poppler/Link.h /usr/include/poppler/NameToCharCode.h /usr/include/poppler/NameToUnicodeTable.h /usr/include/poppler/Object.h /usr/include/poppler/Outline.h /usr/include/poppler/OutputDev.h /usr/include/poppler/PDFDoc.h /usr/include/poppler/PDFDocEncoding.h /usr/include/poppler/PSOutputDev.h /usr/include/poppler/PSTokenizer.h /usr/include/poppler/Page.h /usr/include/poppler/PageTransition.h /usr/include/poppler/Parser.h /usr/include/poppler/PreScanOutputDev.h /usr/include/poppler/ProfileData.h /usr/include/poppler/SecurityHandler.h /usr/include/poppler/Sound.h /usr/include/poppler/SplashOutputDev.h /usr/include/poppler/Stream-CCITT.h /usr/include/poppler/Stream.h /usr/include/poppler/TextOutputDev.h /usr/include/poppler/UTF8.h /usr/include/poppler/UnicodeCClassTables.h /usr/include/poppler/UnicodeCompTables.h /usr/include/poppler/UnicodeDecompTables.h /usr/include/poppler/UnicodeMap.h /usr/include/poppler/UnicodeMapTables.h /usr/include/poppler/UnicodeTypeTable.h /usr/include/poppler/XRef.h /usr/include/poppler/XpdfPluginAPI.h /usr/include/poppler/goo/FixedPoint.h /usr/include/poppler/goo/GooHash.h /usr/include/poppler/goo/GooList.h /usr/include/poppler/goo/GooMutex.h /usr/include/poppler/goo/GooString.h /usr/include/poppler/goo/GooTimer.h /usr/include/poppler/goo/GooVector.h /usr/include/poppler/goo/gfile.h /usr/include/poppler/goo/gmem.h /usr/include/poppler/goo/gtypes.h /usr/include/poppler/poppler-config.h /usr/include/poppler/splash/Splash.h /usr/include/poppler/splash/SplashBitmap.h /usr/include/poppler/splash/SplashClip.h /usr/include/poppler/splash/SplashErrorCodes.h /usr/include/poppler/splash/SplashFTFont.h /usr/include/poppler/splash/SplashFTFontEngine.h /usr/include/poppler/splash/SplashFTFontFile.h /usr/include/poppler/splash/SplashFont.h /usr/include/poppler/splash/SplashFontEngine.h /usr/include/poppler/splash/SplashFontFile.h /usr/include/poppler/splash/SplashFontFileID.h /usr/include/poppler/splash/SplashGlyphBitmap.h /usr/include/poppler/splash/SplashMath.h /usr/include/poppler/splash/SplashPath.h /usr/include/poppler/splash/SplashPattern.h /usr/include/poppler/splash/SplashScreen.h /usr/include/poppler/splash/SplashState.h /usr/include/poppler/splash/SplashT1Font.h /usr/include/poppler/splash/SplashT1FontEngine.h /usr/include/poppler/splash/SplashT1FontFile.h /usr/include/poppler/splash/SplashTypes.h /usr/include/poppler/splash/SplashXPath.h /usr/include/poppler/splash/SplashXPathScanner.h
Joshua Facemyer / Impressus Art wrote:
Jon A. Cruz wrote:
On Oct 20, 2007, at 6:49 PM, Joshua Facemyer / Impressus Art wrote:
Okay, will the same pdf functionality be present then? (Also, is this a workaround to get the thing compiling at a loss of functionality, or is it something that should / will be addressed in a future update to make it compile in an environment that it should without difficulty?)
Someone familiar with the specifics would have to look into it, but I think it's a work-around in losing a bit of functionality...
But from what I recall, it's probably due to us using internals of poppler that are not part of the public API. Get and build poppler yourself and you might have the needed .h, but use standard packing and you probably won't.
Part of me only seeing this recently was that only recently had I gotten a new enough poppler in macports.
I use Gentoo, so my poppler should be "my own" build. Same with Jeff. (Had you figured this out yet, Jeff?)
Is it maybe that some switch needs to be passed to poppler when building it?
JF
Update: on my two gentoo boxes, one won't build the latest SVN with poppler 0.6 and one will. They both have Cairo 1.4.10, and both packages are built with the same use flags.
JF
Got somewhere with this.
I removed the poppler-bindings package, which was the different thing between my installations.
In configure, I get:
checking for POPPLER... yes checking for POPPLER_GLIB... no checking for POPPLER_CAIRO... no
and also:
Enable Poppler-Cairo: yes
Does this mean I have tried to enable it but it doesn't work?
With poppler-bindings installed, it gave me yeses for all three checks, but wouldn't compile.
What am I doing wrong?
Jeff, is this the same for you?
JF
Joshua Facemyer / Impressus Art wrote:
Jon A. Cruz wrote:
On Oct 20, 2007, at 6:49 PM, Joshua Facemyer / Impressus Art wrote:
Okay, will the same pdf functionality be present then? (Also, is this a workaround to get the thing compiling at a loss of functionality, or is it something that should / will be addressed in a future update to make it compile in an environment that it should without difficulty?)
Someone familiar with the specifics would have to look into it, but I think it's a work-around in losing a bit of functionality...
But from what I recall, it's probably due to us using internals of poppler that are not part of the public API. Get and build poppler yourself and you might have the needed .h, but use standard packing and you probably won't.
Part of me only seeing this recently was that only recently had I gotten a new enough poppler in macports.
I use Gentoo, so my poppler should be "my own" build. Same with Jeff. (Had you figured this out yet, Jeff?)
Is it maybe that some switch needs to be passed to poppler when building it?
JF
Update: on my two gentoo boxes, one won't build the latest SVN with poppler 0.6 and one will. They both have Cairo 1.4.10, and both packages are built with the same use flags.
JF
Joshua,
Here's the particulars of poppler-bindings, poppler and cairo on my system:
It would be easier if we knew which package's header file had the define that causes the inkscape build error.
POPPLER-BINDINGS ----------------
# emerge poppler-bindings -pv
These are the packages that would be merged, in order:
Calculating dependencies ..... ..... ........ done! [ebuild R ] app-text/poppler-bindings-0.6.1 USE="cairo gtk qt4 -qt3 -test" 0 kB
Total: 1 package (1 reinstall), Size of downloads: 0 kB thinkpad jtk # emerge poppler-bindings Calculating dependencies ..... ..... ........ done!
Verifying ebuild Manifests...
Emerging (1 of 1) app-text/poppler-bindings-0.6.1 to /
* poppler-0.6.1.tar.gz RMD160 ;-) ... [ ok ] * poppler-0.6.1.tar.gz SHA1 ;-) ... [ ok ] * poppler-0.6.1.tar.gz SHA256 ;-) ... [ ok ] * poppler-0.6.1.tar.gz size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking poppler-0.6.1.tar.gz ;-) ... [ ok ]
Unpacking source... Unpacking poppler-0.6.1.tar.gz to /var/tmp/portage/app-text/poppler-bindings-0.6.1/work
* Applying poppler-0.6-bindings.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/app-text/poppler-bindings-0.6.1/work/poppler-0.6.1' ... * Running aclocal -I m4 ... [ ok ] * Running libtoolize --copy --force --automake ... [ ok ] * Running aclocal -I m4 ... [ ok ] * Running autoconf ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy ... [ ok ] * Running elibtoolize in: poppler-0.6.1 * Applying install-sh-1.5.4.patch ... * Applying sed-1.5.6.patch ...
Source unpacked. Compiling source in /var/tmp/portage/app-text/poppler-bindings-0.6.1/work/poppler-0.6.1 ...
/lib * econf: updating poppler-0.6.1/config.guess with /usr/share/gnuconfig/config.guess * econf: updating poppler-0.6.1/config.sub with /usr/share/gnuconfig/config.sub ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --enable-opi --enable-cairo-output --enable-poppler-glib --disable-poppler-qt --enable-poppler-qt4 --build=i686-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for style of include used by make... GNU checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether i686-pc-linux-gnu-gcc accepts -g... yes checking for i686-pc-linux-gnu-gcc option to accept ISO C89... none needed checking dependency style of i686-pc-linux-gnu-gcc... gcc3 checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ld used by i686-pc-linux-gnu-gcc... /usr/i686-pc-linux-gnu/bin/ld checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognize dependent libraries... pass_all checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++ checking whether we are using the GNU C++ compiler... yes checking whether i686-pc-linux-gnu-g++ accepts -g... yes checking dependency style of i686-pc-linux-gnu-g++... gcc3 checking how to run the C++ preprocessor... i686-pc-linux-gnu-g++ -E checking for i686-pc-linux-gnu-g77... no checking for i686-pc-linux-gnu-xlf... no checking for i686-pc-linux-gnu-f77... no checking for i686-pc-linux-gnu-frt... no checking for i686-pc-linux-gnu-pgf77... no checking for i686-pc-linux-gnu-cf77... no checking for i686-pc-linux-gnu-fort77... no checking for i686-pc-linux-gnu-fl32... no checking for i686-pc-linux-gnu-af77... no checking for i686-pc-linux-gnu-xlf90... no checking for i686-pc-linux-gnu-f90... no checking for i686-pc-linux-gnu-pgf90... no checking for i686-pc-linux-gnu-pghpf... no checking for i686-pc-linux-gnu-epcf90... no checking for i686-pc-linux-gnu-gfortran... i686-pc-linux-gnu-gfortran checking whether we are using the GNU Fortran 77 compiler... yes checking whether i686-pc-linux-gnu-gfortran accepts -g... yes checking the maximum length of command line arguments... 98304 checking command to parse /usr/bin/nm -B output from i686-pc-linux-gnu-gcc object... ok checking for objdir... .libs checking for i686-pc-linux-gnu-ar... i686-pc-linux-gnu-ar checking for i686-pc-linux-gnu-ranlib... i686-pc-linux-gnu-ranlib checking for i686-pc-linux-gnu-strip... i686-pc-linux-gnu-strip checking for correct ltmain.sh version... yes checking if i686-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no checking for i686-pc-linux-gnu-gcc option to produce PIC... -fPIC checking if i686-pc-linux-gnu-gcc PIC flag -fPIC works... yes checking if i686-pc-linux-gnu-gcc static flag -static works... yes checking if i686-pc-linux-gnu-gcc supports -c -o file.o... yes checking whether the i686-pc-linux-gnu-gcc linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by i686-pc-linux-gnu-g++... /usr/i686-pc-linux-gnu/bin/ld checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes checking whether the i686-pc-linux-gnu-g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes checking for i686-pc-linux-gnu-g++ option to produce PIC... -fPIC checking if i686-pc-linux-gnu-g++ PIC flag -fPIC works... yes checking if i686-pc-linux-gnu-g++ static flag -static works... yes checking if i686-pc-linux-gnu-g++ supports -c -o file.o... yes checking whether the i686-pc-linux-gnu-g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for i686-pc-linux-gnu-gfortran option to produce PIC... -fPIC checking if i686-pc-linux-gnu-gfortran PIC flag -fPIC works... yes checking if i686-pc-linux-gnu-gfortran static flag -static works... yes checking if i686-pc-linux-gnu-gfortran supports -c -o file.o... yes checking whether the i686-pc-linux-gnu-gfortran linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for i686-pc-linux-gnu-gcc... (cached) i686-pc-linux-gnu-gcc checking whether we are using the GNU C compiler... (cached) yes checking whether i686-pc-linux-gnu-gcc accepts -g... (cached) yes checking for i686-pc-linux-gnu-gcc option to accept ISO C89... (cached) none needed checking dependency style of i686-pc-linux-gnu-gcc... (cached) gcc3 checking whether we are using the GNU C++ compiler... (cached) yes checking whether i686-pc-linux-gnu-g++ accepts -g... (cached) yes checking dependency style of i686-pc-linux-gnu-g++... (cached) gcc3 checking for library containing strerror... none required checking for i686-pc-linux-gnu-gcc option to accept ISO C99... -std=gnu99 checking for i686-pc-linux-gnu-gcc -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu99 checking whether we are using the GNU C++ compiler... (cached) yes checking whether i686-pc-linux-gnu-g++ accepts -g... (cached) yes checking dependency style of i686-pc-linux-gnu-g++... (cached) gcc3 checking for a BSD-compatible install... /usr/bin/install -c checking for gettimeofday... yes checking for X... libraries , headers checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... yes checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking for gethostbyname... (cached) yes checking for popen... yes checking for mkstemp... yes checking for mkstemps... no checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... 64 checking for _LARGEFILE_SOURCE value needed for large files... no checking for fseek64... no checking for ftell64... no checking for libjpeg6b... no checking for libjpeg... -ljpeg checking for i686-pc-linux-gnu-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for FREETYPE... yes checking for FONTCONFIG... yes checking for CAIRO... yes checking for POPPLER_GLIB... yes checking for glib-mkenums... /usr/bin/glib-mkenums checking for POPPLER_QT4... yes checking for GTK_TEST... yes checking for ABIWORD... yes configure: creating ./config.status config.status: creating Makefile config.status: creating goo/Makefile config.status: creating fofi/Makefile config.status: creating splash/Makefile config.status: creating poppler/Makefile config.status: creating utils/Makefile config.status: creating glib/Makefile config.status: creating glib/poppler-features.h config.status: creating glib/reference/Makefile config.status: creating glib/demo/Makefile config.status: creating test/Makefile config.status: creating qt/Makefile config.status: creating qt4/Makefile config.status: creating qt4/src/Makefile config.status: creating qt4/tests/Makefile config.status: creating poppler.pc config.status: creating poppler-cairo.pc config.status: creating poppler-splash.pc config.status: creating poppler-glib.pc config.status: creating poppler-qt.pc config.status: creating poppler-qt4.pc config.status: creating config.h config.status: creating poppler/poppler-config.h config.status: poppler/poppler-config.h is unchanged config.status: executing depfiles commands
Building poppler with support for: splash output: yes cairo output: yes abiword output: yes qt wrapper: no qt4 wrapper: yes glib wrapper: yes use gtk-doc: no use libjpeg: yes use zlib: no command line utils: yes (...)
# equery files poppler-bindings [ Searching for packages matching poppler-bindings... ] * Contents of app-text/poppler-bindings-0.6.1: /usr /usr/include /usr/include/poppler /usr/include/poppler/glib /usr/include/poppler/glib/poppler-action.h /usr/include/poppler/glib/poppler-attachment.h /usr/include/poppler/glib/poppler-document.h /usr/include/poppler/glib/poppler-enums.h /usr/include/poppler/glib/poppler-features.h /usr/include/poppler/glib/poppler-form-field.h /usr/include/poppler/glib/poppler-page.h /usr/include/poppler/glib/poppler.h /usr/include/poppler/qt4 /usr/include/poppler/qt4/poppler-annotation.h /usr/include/poppler/qt4/poppler-form.h /usr/include/poppler/qt4/poppler-link.h /usr/include/poppler/qt4/poppler-page-transition.h /usr/include/poppler/qt4/poppler-qt4.h /usr/lib /usr/lib/libpoppler-glib.a /usr/lib/libpoppler-glib.la /usr/lib/libpoppler-glib.so -> libpoppler-glib.so.2.0.0 /usr/lib/libpoppler-glib.so.2 -> libpoppler-glib.so.2.0.0 /usr/lib/libpoppler-glib.so.2.0.0 /usr/lib/libpoppler-qt4.a /usr/lib/libpoppler-qt4.la /usr/lib/libpoppler-qt4.so -> libpoppler-qt4.so.2.0.0 /usr/lib/libpoppler-qt4.so.2 -> libpoppler-qt4.so.2.0.0 /usr/lib/libpoppler-qt4.so.2.0.0 /usr/lib/pkgconfig /usr/lib/pkgconfig/poppler-cairo.pc /usr/lib/pkgconfig/poppler-glib.pc /usr/lib/pkgconfig/poppler-qt4.pc /usr/share /usr/share/gtk-doc /usr/share/gtk-doc/html /usr/share/gtk-doc/html/poppler /usr/share/gtk-doc/html/poppler/ch01.html /usr/share/gtk-doc/html/poppler/home.png /usr/share/gtk-doc/html/poppler/index.html /usr/share/gtk-doc/html/poppler/index.sgml /usr/share/gtk-doc/html/poppler/left.png /usr/share/gtk-doc/html/poppler/poppler-poppler-action.html /usr/share/gtk-doc/html/poppler/poppler-poppler-attachment.html /usr/share/gtk-doc/html/poppler/poppler-poppler-document.html /usr/share/gtk-doc/html/poppler/poppler-poppler-enums.html /usr/share/gtk-doc/html/poppler/poppler-poppler-form-field.html /usr/share/gtk-doc/html/poppler/poppler-poppler-page.html /usr/share/gtk-doc/html/poppler/poppler-poppler.html /usr/share/gtk-doc/html/poppler/poppler.devhelp /usr/share/gtk-doc/html/poppler/poppler.devhelp2 /usr/share/gtk-doc/html/poppler/right.png /usr/share/gtk-doc/html/poppler/style.css /usr/share/gtk-doc/html/poppler/up.png
POPPLER -------
# emerge poppler -pv
These are the packages that would be merged, in order:
Calculating dependencies ..... ..... ........ done! [ebuild R ] app-text/poppler-0.6.1 USE="jpeg zlib -cjk" 0 kB
Total: 1 package (1 reinstall), Size of downloads: 0 kB
# emerge poppler Calculating dependencies ..... ..... ........ done!
Verifying ebuild Manifests...
Emerging (1 of 1) app-text/poppler-0.6.1 to /
* poppler-0.6.1.tar.gz RMD160 ;-) ... [ ok ] * poppler-0.6.1.tar.gz SHA1 ;-) ... [ ok ] * poppler-0.6.1.tar.gz SHA256 ;-) ... [ ok ] * poppler-0.6.1.tar.gz size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking poppler-0.6.1.tar.gz ;-) ... [ ok ]
Unpacking source... Unpacking poppler-0.6.1.tar.gz to /var/tmp/portage/app-text/poppler-0.6.1/work Source unpacked. Compiling source in /var/tmp/portage/app-text/poppler-0.6.1/work/poppler-0.6.1 ...
* econf: updating poppler-0.6.1/config.guess with /usr/share/gnuconfig/config.guess * econf: updating poppler-0.6.1/config.sub with /usr/share/gnuconfig/config.sub ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-poppler-qt4 --disable-poppler-glib --disable-poppler-qt --disable-gtk-test --enable-opi --disable-cairo-output --enable-xpdf-headers --enable-libjpeg --enable-zlib --build=i686-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for style of include used by make... GNU checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether i686-pc-linux-gnu-gcc accepts -g... yes checking for i686-pc-linux-gnu-gcc option to accept ISO C89... none needed checking dependency style of i686-pc-linux-gnu-gcc... gcc3 checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ld used by i686-pc-linux-gnu-gcc... /usr/i686-pc-linux-gnu/bin/ld checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognize dependent libraries... pass_all checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++ checking whether we are using the GNU C++ compiler... yes checking whether i686-pc-linux-gnu-g++ accepts -g... yes checking dependency style of i686-pc-linux-gnu-g++... gcc3 checking how to run the C++ preprocessor... i686-pc-linux-gnu-g++ -E checking for i686-pc-linux-gnu-g77... no checking for i686-pc-linux-gnu-xlf... no checking for i686-pc-linux-gnu-f77... no checking for i686-pc-linux-gnu-frt... no checking for i686-pc-linux-gnu-pgf77... no checking for i686-pc-linux-gnu-cf77... no checking for i686-pc-linux-gnu-fort77... no checking for i686-pc-linux-gnu-fl32... no checking for i686-pc-linux-gnu-af77... no checking for i686-pc-linux-gnu-xlf90... no checking for i686-pc-linux-gnu-f90... no checking for i686-pc-linux-gnu-pgf90... no checking for i686-pc-linux-gnu-pghpf... no checking for i686-pc-linux-gnu-epcf90... no checking for i686-pc-linux-gnu-gfortran... i686-pc-linux-gnu-gfortran checking whether we are using the GNU Fortran 77 compiler... yes checking whether i686-pc-linux-gnu-gfortran accepts -g... yes checking the maximum length of command line arguments... 98304 checking command to parse /usr/bin/nm -B output from i686-pc-linux-gnu-gcc object... ok checking for objdir... .libs checking for i686-pc-linux-gnu-ar... i686-pc-linux-gnu-ar checking for i686-pc-linux-gnu-ranlib... i686-pc-linux-gnu-ranlib checking for i686-pc-linux-gnu-strip... i686-pc-linux-gnu-strip checking if i686-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no checking for i686-pc-linux-gnu-gcc option to produce PIC... -fPIC checking if i686-pc-linux-gnu-gcc PIC flag -fPIC works... yes checking if i686-pc-linux-gnu-gcc static flag -static works... yes checking if i686-pc-linux-gnu-gcc supports -c -o file.o... yes checking whether the i686-pc-linux-gnu-gcc linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by i686-pc-linux-gnu-g++... /usr/i686-pc-linux-gnu/bin/ld checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes checking whether the i686-pc-linux-gnu-g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes checking for i686-pc-linux-gnu-g++ option to produce PIC... -fPIC checking if i686-pc-linux-gnu-g++ PIC flag -fPIC works... yes checking if i686-pc-linux-gnu-g++ static flag -static works... yes checking if i686-pc-linux-gnu-g++ supports -c -o file.o... yes checking whether the i686-pc-linux-gnu-g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for i686-pc-linux-gnu-gfortran option to produce PIC... -fPIC checking if i686-pc-linux-gnu-gfortran PIC flag -fPIC works... yes checking if i686-pc-linux-gnu-gfortran static flag -static works... yes checking if i686-pc-linux-gnu-gfortran supports -c -o file.o... yes checking whether the i686-pc-linux-gnu-gfortran linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for i686-pc-linux-gnu-gcc... (cached) i686-pc-linux-gnu-gcc checking whether we are using the GNU C compiler... (cached) yes checking whether i686-pc-linux-gnu-gcc accepts -g... (cached) yes checking for i686-pc-linux-gnu-gcc option to accept ISO C89... (cached) none needed checking dependency style of i686-pc-linux-gnu-gcc... (cached) gcc3 checking whether we are using the GNU C++ compiler... (cached) yes checking whether i686-pc-linux-gnu-g++ accepts -g... (cached) yes checking dependency style of i686-pc-linux-gnu-g++... (cached) gcc3 checking for library containing strerror... none required checking for i686-pc-linux-gnu-gcc option to accept ISO C99... -std=gnu99 checking for i686-pc-linux-gnu-gcc -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu99 checking whether we are using the GNU C++ compiler... (cached) yes checking whether i686-pc-linux-gnu-g++ accepts -g... (cached) yes checking dependency style of i686-pc-linux-gnu-g++... (cached) gcc3 checking for a BSD-compatible install... /usr/bin/install -c checking for gettimeofday... yes checking for X... libraries , headers checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... yes checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking for gethostbyname... (cached) yes checking for popen... yes checking for mkstemp... yes checking for mkstemps... no checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... 64 checking for _LARGEFILE_SOURCE value needed for large files... no checking for fseek64... no checking for ftell64... no checking for inflate in -lz... yes checking zlib.h usability... yes checking zlib.h presence... yes checking for zlib.h... yes checking for libjpeg6b... no checking for libjpeg... -ljpeg checking for i686-pc-linux-gnu-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for FREETYPE... yes checking for FONTCONFIG... yes checking for ABIWORD... yes configure: creating ./config.status config.status: creating Makefile config.status: creating goo/Makefile config.status: creating fofi/Makefile config.status: creating splash/Makefile config.status: creating poppler/Makefile config.status: creating utils/Makefile config.status: creating glib/Makefile config.status: creating glib/poppler-features.h config.status: creating glib/reference/Makefile config.status: creating glib/demo/Makefile config.status: creating test/Makefile config.status: creating qt/Makefile config.status: creating qt4/Makefile config.status: creating qt4/src/Makefile config.status: creating qt4/tests/Makefile config.status: creating poppler.pc config.status: creating poppler-cairo.pc config.status: creating poppler-splash.pc config.status: creating poppler-glib.pc config.status: creating poppler-qt.pc config.status: creating poppler-qt4.pc config.status: creating config.h config.status: creating poppler/poppler-config.h config.status: poppler/poppler-config.h is unchanged config.status: executing depfiles commands
Building poppler with support for: splash output: yes cairo output: no abiword output: yes qt wrapper: no qt4 wrapper: no glib wrapper: no use gtk-doc: no use libjpeg: yes use zlib: yes command line utils: yes (...)
# equery files poppler [ Searching for packages matching poppler... ] * Contents of app-text/poppler-0.6.1: /usr /usr/bin /usr/bin/pdffonts /usr/bin/pdfimages /usr/bin/pdfinfo /usr/bin/pdftoabw /usr/bin/pdftohtml /usr/bin/pdftoppm /usr/bin/pdftops /usr/bin/pdftotext /usr/include /usr/include/poppler /usr/include/poppler/Annot.h /usr/include/poppler/Array.h /usr/include/poppler/BaseFile.h /usr/include/poppler/BuiltinFont.h /usr/include/poppler/BuiltinFontTables.h /usr/include/poppler/CMap.h /usr/include/poppler/Catalog.h /usr/include/poppler/CharCodeToUnicode.h /usr/include/poppler/CharTypes.h /usr/include/poppler/CompactFontTables.h /usr/include/poppler/Decrypt.h /usr/include/poppler/Dict.h /usr/include/poppler/Error.h /usr/include/poppler/ErrorCodes.h /usr/include/poppler/FontEncodingTables.h /usr/include/poppler/FontInfo.h /usr/include/poppler/Form.h /usr/include/poppler/Function.cc /usr/include/poppler/Function.h /usr/include/poppler/Gfx.h /usr/include/poppler/GfxFont.h /usr/include/poppler/GfxState.h /usr/include/poppler/GlobalParams.h /usr/include/poppler/JArithmeticDecoder.h /usr/include/poppler/JBIG2Stream.h /usr/include/poppler/JPXStream.h /usr/include/poppler/Lexer.h /usr/include/poppler/Link.h /usr/include/poppler/NameToCharCode.h /usr/include/poppler/NameToUnicodeTable.h /usr/include/poppler/Object.h /usr/include/poppler/Outline.h /usr/include/poppler/OutputDev.h /usr/include/poppler/PDFDoc.h /usr/include/poppler/PDFDocEncoding.h /usr/include/poppler/PSOutputDev.h /usr/include/poppler/PSTokenizer.h /usr/include/poppler/Page.h /usr/include/poppler/PageTransition.h /usr/include/poppler/Parser.h /usr/include/poppler/PreScanOutputDev.h /usr/include/poppler/ProfileData.h /usr/include/poppler/SecurityHandler.h /usr/include/poppler/Sound.h /usr/include/poppler/SplashOutputDev.h /usr/include/poppler/Stream-CCITT.h /usr/include/poppler/Stream.h /usr/include/poppler/TextOutputDev.h /usr/include/poppler/UTF8.h /usr/include/poppler/UnicodeCClassTables.h /usr/include/poppler/UnicodeCompTables.h /usr/include/poppler/UnicodeDecompTables.h /usr/include/poppler/UnicodeMap.h /usr/include/poppler/UnicodeMapTables.h /usr/include/poppler/UnicodeTypeTable.h /usr/include/poppler/XRef.h /usr/include/poppler/XpdfPluginAPI.h /usr/include/poppler/goo /usr/include/poppler/goo/FixedPoint.h /usr/include/poppler/goo/GooHash.h /usr/include/poppler/goo/GooList.h /usr/include/poppler/goo/GooMutex.h /usr/include/poppler/goo/GooString.h /usr/include/poppler/goo/GooTimer.h /usr/include/poppler/goo/GooVector.h /usr/include/poppler/goo/gfile.h /usr/include/poppler/goo/gmem.h /usr/include/poppler/goo/gtypes.h /usr/include/poppler/poppler-config.h /usr/include/poppler/splash /usr/include/poppler/splash/Splash.h /usr/include/poppler/splash/SplashBitmap.h /usr/include/poppler/splash/SplashClip.h /usr/include/poppler/splash/SplashErrorCodes.h /usr/include/poppler/splash/SplashFTFont.h /usr/include/poppler/splash/SplashFTFontEngine.h /usr/include/poppler/splash/SplashFTFontFile.h /usr/include/poppler/splash/SplashFont.h /usr/include/poppler/splash/SplashFontEngine.h /usr/include/poppler/splash/SplashFontFile.h /usr/include/poppler/splash/SplashFontFileID.h /usr/include/poppler/splash/SplashGlyphBitmap.h /usr/include/poppler/splash/SplashMath.h /usr/include/poppler/splash/SplashPath.h /usr/include/poppler/splash/SplashPattern.h /usr/include/poppler/splash/SplashScreen.h /usr/include/poppler/splash/SplashState.h /usr/include/poppler/splash/SplashT1Font.h /usr/include/poppler/splash/SplashT1FontEngine.h /usr/include/poppler/splash/SplashT1FontFile.h /usr/include/poppler/splash/SplashTypes.h /usr/include/poppler/splash/SplashXPath.h /usr/include/poppler/splash/SplashXPathScanner.h /usr/lib /usr/lib/libpoppler.a /usr/lib/libpoppler.la /usr/lib/libpoppler.so -> libpoppler.so.2.0.0 /usr/lib/libpoppler.so.2 -> libpoppler.so.2.0.0 /usr/lib/libpoppler.so.2.0.0 /usr/lib/pkgconfig /usr/lib/pkgconfig/poppler-splash.pc /usr/lib/pkgconfig/poppler.pc /usr/share /usr/share/doc /usr/share/doc/poppler-0.6.1 /usr/share/doc/poppler-0.6.1/AUTHORS.bz2 /usr/share/doc/poppler-0.6.1/ChangeLog.bz2 /usr/share/doc/poppler-0.6.1/NEWS.bz2 /usr/share/doc/poppler-0.6.1/README-XPDF.bz2 /usr/share/doc/poppler-0.6.1/README.bz2 /usr/share/doc/poppler-0.6.1/TODO.bz2 /usr/share/man /usr/share/man/man1 /usr/share/man/man1/pdffonts.1.bz2 /usr/share/man/man1/pdfimages.1.bz2 /usr/share/man/man1/pdfinfo.1.bz2 /usr/share/man/man1/pdftohtml.1.bz2 /usr/share/man/man1/pdftoppm.1.bz2 /usr/share/man/man1/pdftops.1.bz2 /usr/share/man/man1/pdftotext.1.bz2
CAIRO -----
# equery files cairo | grep \.h /usr/include/cairo/cairo-deprecated.h /usr/include/cairo/cairo-features.h /usr/include/cairo/cairo-ft.h /usr/include/cairo/cairo-glitz.h /usr/include/cairo/cairo-pdf.h /usr/include/cairo/cairo-ps.h /usr/include/cairo/cairo-svg.h /usr/include/cairo/cairo-xlib-xrender.h /usr/include/cairo/cairo-xlib.h /usr/include/cairo/cairo.h
# emerge cairo -pv
These are the packages that would be merged, in order:
Calculating dependencies ..... ..... ........ done! [ebuild R ] x11-libs/cairo-1.4.10 USE="X glitz newspr opengl svg -debug -directfb -doc -xcb" 0 kB [1]
Total: 1 package (1 reinstall), Size of downloads: 0 kB Portage tree and overlays: [0] /usr/portage [1] /usr/portage/local/layman/xeffects
On Oct 23, 2007, at 9:59 PM, Jeff Kowalczyk wrote:
Joshua,
Here's the particulars of poppler-bindings, poppler and cairo on my system:
It would be easier if we knew which package's header file had the define that causes the inkscape build error.
I believe that the key is the file CairoOutputDev.h
On systems that have compile working, check what package owns that .h file.
Jon A. Cruz wrote:
On Oct 23, 2007, at 9:59 PM, Jeff Kowalczyk wrote:
Joshua,
Here's the particulars of poppler-bindings, poppler and cairo on my
system:
It would be easier if we knew which package's header file had the define
that causes the inkscape build error.
I believe that the key is the file CairoOutputDev.h
On systems that have compile working, check what package owns that .h file.
Nobody owns it, as far as I can tell. It doesn't live anywhere I can find, either with or without poppler-bindings installed. But then, neither of my machines actually compile with poppler support, I think I've determined :) So I'm no help.
However, poppler appears to provide the file. I'm not knowledgeable about these things, but here:
http://webcvs.freedesktop.org/poppler/poppler/poppler/CairoOutputDev.h?view=...
it shows as being part of poppler, right?
JF
This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
I believe that the key is the file CairoOutputDev.h
On systems that have compile working, check what package owns that .h file.
Nobody owns it, as far as I can tell. It doesn't live anywhere I can find, either with or without poppler-bindings installed. But then, neither of my machines actually compile with poppler support, I think I've determined :) So I'm no help.
However, poppler appears to provide the file. I'm not knowledgeable about these things, but here:
http://webcvs.freedesktop.org/poppler/poppler/poppler/CairoOutputDev.h?view=...
it shows as being part of poppler, right?
JF
Also, when I build poppler, the default on Gentoo appears to be to install with
--disable-poppler-glib --disable-cairo-output
no use flags available to change this.
JF
On Oct 24, 2007, at 9:40 PM, Joshua Facemyer / Impressus Art wrote:
Nobody owns it, as far as I can tell. It doesn't live anywhere I can find, either with or without poppler-bindings installed. But then, neither of my machines actually compile with poppler support, I think I've determined :) So I'm no help.
However, poppler appears to provide the file. I'm not knowledgeable about these things, but here:
http://webcvs.freedesktop.org/poppler/poppler/poppler/ CairoOutputDev.h?view=log&pathrev=MAIN
it shows as being part of poppler, right?
It might mean that it is an internal part of poppler, and not a public include file.
Jon A. Cruz wrote:
On Oct 24, 2007, at 9:40 PM, Joshua Facemyer / Impressus Art wrote:
Nobody owns it, as far as I can tell. It doesn't live anywhere I can
find, either with or without poppler-bindings installed. But then,
neither of my machines actually compile with poppler support, I think
I've determined :) So I'm no help.
However, poppler appears to provide the file. I'm not knowledgeable
about these things, but here:
http://webcvs.freedesktop.org/poppler/poppler/poppler/CairoOutputDev.h?view=... http://webcvs.freedesktop.org/poppler/poppler/poppler/CairoOutputDev.h?view=log&pathrev=MAIN
it shows as being part of poppler, right?
It might mean that it is an internal part of poppler, and not a public include file.
Well, it appears that if you copy the header file from the poppler tarball to /usr/include/poppler, it compiles no problem (make sure you have poppler-bindings installed on a gentoo system).
The confusion about poppler-bindings, I find, is only a gentoo separation. I've filed a bug report there, but it sounded like others where having this problem also. So maybe poppler isn't installing it by default? But maybe people aren't using the previously mentioned switches when compiling poppler?
Hope that helps people - Jeff, any luck?
JF
Jon A. Cruz wrote:
On Oct 24, 2007, at 9:40 PM, Joshua Facemyer / Impressus Art wrote:
Nobody owns it, as far as I can tell. It doesn't live anywhere I can
find, either with or without poppler-bindings installed. But then,
neither of my machines actually compile with poppler support, I think
I've determined :) So I'm no help.
However, poppler appears to provide the file. I'm not knowledgeable
about these things, but here:
http://webcvs.freedesktop.org/poppler/poppler/poppler/CairoOutputDev.h?view=... http://webcvs.freedesktop.org/poppler/poppler/poppler/CairoOutputDev.h?view=log&pathrev=MAIN
it shows as being part of poppler, right?
It might mean that it is an internal part of poppler, and not a public include file.
OK, so a guy on poppler's irc told me "bad inkscape svn for using a private header".
He said it should use the glib frontend for that functionality.
Miklos, is that your area?
JF
On 10/25/07, Joshua Facemyer / Impressus Art <faceman@...1574...> wrote:
Jon A. Cruz wrote:
It might mean that it is an internal part of poppler, and not a public include file.
OK, so a guy on poppler's irc told me "bad inkscape svn for using a private header".
He said it should use the glib frontend for that functionality.
The poppler PDF importer was coded to introduce the least possible number of new package dependencies into Inkscape, so that's why we're using CairoOutputDev instead of calling the glib wrapper functions to generate a page preview using CairoOutputDev... But if we took poppler-glib on our dependency list, modifying the pdf import dialog code to use poppler-glib for preview would be straightforward.
Regards, miklos
Miklós Erdélyi wrote:
On 10/25/07, Joshua Facemyer / Impressus Art <faceman@...1574...> wrote:
Jon A. Cruz wrote:
It might mean that it is an internal part of poppler, and not a public include file.
OK, so a guy on poppler's irc told me "bad inkscape svn for using a private header".
He said it should use the glib frontend for that functionality.
The poppler PDF importer was coded to introduce the least possible number of new package dependencies into Inkscape, so that's why we're using CairoOutputDev instead of calling the glib wrapper functions to generate a page preview using CairoOutputDev... But if we took poppler-glib on our dependency list, modifying the pdf import dialog code to use poppler-glib for preview would be straightforward.
Regards, miklos
But then we'll have the perpetual problem of people not having the proper header file, which is unsupported by poppler as a public file.
Considering the importance of PDF functionality (looking over the list archives, back in the summer, bulia said something to the effect that Inkscape was now able to compete with professional apps because of the new pdf stuff) I think the dependency on poppler-glib is not a significant disadvantage, especially if the option to not compile with poppler support exists. (Wasn't there talk recently of having a compile-time switch determine whether to include poppler or internal pdf support? Not a perfect solution, but might help if people are determined to keep deps down.)
Also, I'd guess that many gtk apps which use/will use poppler will depend on poppler-glib functions anyway - but I really don't know, so can't say for certain.
The problem here is not just that the missing header prevents functionality. The problem is that it breaks compilation. If poppler is installed correctly (according to poppler devs), and you compile Inkscape with poppler support, it fails.
I understand the need to keep dependencies to a minimum; however, such powerful functionality may merit a new set of dependencies. Maybe it's time to reconsider?
JF
Joshua Facemyer / Impressus Art wrote:
But then we'll have the perpetual problem of people not having the proper header file, which is unsupported by poppler as a public file.
Considering the importance of PDF functionality (looking over the list archives, back in the summer, bulia said something to the effect that Inkscape was now able to compete with professional apps because of the new pdf stuff) I think the dependency on poppler-glib is not a significant disadvantage, especially if the option to not compile with poppler support exists. (Wasn't there talk recently of having a compile-time switch determine whether to include poppler or internal pdf support? Not a perfect solution, but might help if people are determined to keep deps down.)
Also, I'd guess that many gtk apps which use/will use poppler will depend on poppler-glib functions anyway - but I really don't know, so can't say for certain.
The problem here is not just that the missing header prevents functionality. The problem is that it breaks compilation. If poppler is installed correctly (according to poppler devs), and you compile Inkscape with poppler support, it fails.
I understand the need to keep dependencies to a minimum; however, such powerful functionality may merit a new set of dependencies. Maybe it's time to reconsider?
Would it be possible to resolve this issue from inkscape's side of the poppler issue soon?
I've been using inkscape-0.45.1 for about three months, and I'm eager to resume using the trunk, especially in the run-up to 0.46. Thanks.
I realize this is not going to make me well-liked, but I'd like to bring this subject up again before the next release.
The problem is that on some linux distros (at least Gentoo, I know for certain) there will be broken poppler functionality.
I don't think it's enough to say that we don't want to create more dependencies - if functionality requires a dependency, it's kind of necessary to have that dep.
I know that I can work around it, but I don't think it's a good thing to force people to come up with a workaround for pdf support.
JF
Jeff Kowalczyk wrote:
Joshua Facemyer / Impressus Art wrote:
But then we'll have the perpetual problem of people not having the proper header file, which is unsupported by poppler as a public file.
Considering the importance of PDF functionality (looking over the list archives, back in the summer, bulia said something to the effect that Inkscape was now able to compete with professional apps because of the new pdf stuff) I think the dependency on poppler-glib is not a significant disadvantage, especially if the option to not compile with poppler support exists. (Wasn't there talk recently of having a compile-time switch determine whether to include poppler or internal pdf support? Not a perfect solution, but might help if people are determined to keep deps down.)
Also, I'd guess that many gtk apps which use/will use poppler will depend on poppler-glib functions anyway - but I really don't know, so can't say for certain.
The problem here is not just that the missing header prevents functionality. The problem is that it breaks compilation. If poppler is installed correctly (according to poppler devs), and you compile Inkscape with poppler support, it fails.
I understand the need to keep dependencies to a minimum; however, such powerful functionality may merit a new set of dependencies. Maybe it's time to reconsider?
Would it be possible to resolve this issue from inkscape's side of the poppler issue soon?
I've been using inkscape-0.45.1 for about three months, and I'm eager to resume using the trunk, especially in the run-up to 0.46. Thanks.
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Can we check for this in configure? Then those who have it would get it, and others would not.
--Ted
On Mon, 2008-01-28 at 14:34 -0600, Joshua Facemyer / Impressus Art wrote:
I realize this is not going to make me well-liked, but I'd like to bring this subject up again before the next release.
The problem is that on some linux distros (at least Gentoo, I know for certain) there will be broken poppler functionality.
I don't think it's enough to say that we don't want to create more dependencies - if functionality requires a dependency, it's kind of necessary to have that dep.
I know that I can work around it, but I don't think it's a good thing to force people to come up with a workaround for pdf support.
JF
Jeff Kowalczyk wrote:
Joshua Facemyer / Impressus Art wrote:
But then we'll have the perpetual problem of people not having the proper header file, which is unsupported by poppler as a public file.
Considering the importance of PDF functionality (looking over the list archives, back in the summer, bulia said something to the effect that Inkscape was now able to compete with professional apps because of the new pdf stuff) I think the dependency on poppler-glib is not a significant disadvantage, especially if the option to not compile with poppler support exists. (Wasn't there talk recently of having a compile-time switch determine whether to include poppler or internal pdf support? Not a perfect solution, but might help if people are determined to keep deps down.)
Also, I'd guess that many gtk apps which use/will use poppler will depend on poppler-glib functions anyway - but I really don't know, so can't say for certain.
The problem here is not just that the missing header prevents functionality. The problem is that it breaks compilation. If poppler is installed correctly (according to poppler devs), and you compile Inkscape with poppler support, it fails.
I understand the need to keep dependencies to a minimum; however, such powerful functionality may merit a new set of dependencies. Maybe it's time to reconsider?
Would it be possible to resolve this issue from inkscape's side of the poppler issue soon?
I've been using inkscape-0.45.1 for about three months, and I'm eager to resume using the trunk, especially in the run-up to 0.46. Thanks.
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
The problem is not that they *don't have* poppler, the problem is that some distros don't install the private header files, which correct according to poppler design. So poppler is found, but the compile breaks because it's looking for a header file that's missing.
The appropriate way to use poppler in this circumstance is through poppler-glib. Then, if dependencies (such as poppler-glib) are a concern for a particular distro, they can turn off poppler support. However, if Inkscape wants to have pdf support by default, it should require the appropriate packages by default.
This should also save Inkscape devs trouble in the future when poppler internals change - the glib functions will remain constant.
JF
Ted Gould wrote:
Can we check for this in configure? Then those who have it would get it, and others would not.
--TedOn Mon, 2008-01-28 at 14:34 -0600, Joshua Facemyer / Impressus Art wrote:
I realize this is not going to make me well-liked, but I'd like to bring this subject up again before the next release.
The problem is that on some linux distros (at least Gentoo, I know for certain) there will be broken poppler functionality.
I don't think it's enough to say that we don't want to create more dependencies - if functionality requires a dependency, it's kind of necessary to have that dep.
I know that I can work around it, but I don't think it's a good thing to force people to come up with a workaround for pdf support.
JF
Jeff Kowalczyk wrote:
Joshua Facemyer / Impressus Art wrote:
But then we'll have the perpetual problem of people not having the proper header file, which is unsupported by poppler as a public file.
Considering the importance of PDF functionality (looking over the list archives, back in the summer, bulia said something to the effect that Inkscape was now able to compete with professional apps because of the new pdf stuff) I think the dependency on poppler-glib is not a significant disadvantage, especially if the option to not compile with poppler support exists. (Wasn't there talk recently of having a compile-time switch determine whether to include poppler or internal pdf support? Not a perfect solution, but might help if people are determined to keep deps down.)
Also, I'd guess that many gtk apps which use/will use poppler will depend on poppler-glib functions anyway - but I really don't know, so can't say for certain.
The problem here is not just that the missing header prevents functionality. The problem is that it breaks compilation. If poppler is installed correctly (according to poppler devs), and you compile Inkscape with poppler support, it fails.
I understand the need to keep dependencies to a minimum; however, such powerful functionality may merit a new set of dependencies. Maybe it's time to reconsider?
Would it be possible to resolve this issue from inkscape's side of the poppler issue soon?
I've been using inkscape-0.45.1 for about three months, and I'm eager to resume using the trunk, especially in the run-up to 0.46. Thanks.
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Wed, 2008-01-30 at 15:00 -0600, Joshua Facemyer / Impressus Art wrote:
The problem is not that they *don't have* poppler, the problem is that some distros don't install the private header files, which correct according to poppler design. So poppler is found, but the compile breaks because it's looking for a header file that's missing.
The appropriate way to use poppler in this circumstance is through poppler-glib. Then, if dependencies (such as poppler-glib) are a concern for a particular distro, they can turn off poppler support. However, if Inkscape wants to have pdf support by default, it should require the appropriate packages by default.
This should also save Inkscape devs trouble in the future when poppler internals change - the glib functions will remain constant.
So, are we correctly using the right functions and have the wrong dependency or we're not using the right functions?
--Ted
(Just realized I didn't send this to the list)
I am not a programmer, I would not know where to look or what to look for to find out for sure.
I do know what I've been told or what's obvious:
- config finds poppler if it's installed but fails to compile if the header file CairoOutputDev.h is not installed - per poppler people, CairoOutputDev.h is private and should not be installed - per poppler people, the appropriate way to hook into poppler is through the poppler glib bindings - Inkscape doesn't use the glib bindings to prevent further dependencies - some distros (at least Gentoo, likely others) install poppler without the private header CairoOutputDev.h, so compile breaks unless it's manually installed
So from what I understand, Inkscape should be hooking into poppler through the glib bindings rather than through the private header file if we want to be compatible with the way poppler is built and meant to be installed.
Sorry to be a pain in the butt about this, but I really think this needs to be fixed to avoid some future bugs. I remember that someone told me that not all the functions we need are available in the bindings, but I think the actual reason was the avoidance of additional deps.
Thanks for taking the time to ask about it, Ted! I know everyone's busy getting the release ready (in addition to real life), and your time is important, so really, thanks.
JF
Ted Gould wrote:
On Wed, 2008-01-30 at 15:00 -0600, Joshua Facemyer / Impressus Art wrote:
The problem is not that they *don't have* poppler, the problem is that some distros don't install the private header files, which correct according to poppler design. So poppler is found, but the compile breaks because it's looking for a header file that's missing.
The appropriate way to use poppler in this circumstance is through poppler-glib. Then, if dependencies (such as poppler-glib) are a concern for a particular distro, they can turn off poppler support. However, if Inkscape wants to have pdf support by default, it should require the appropriate packages by default.
This should also save Inkscape devs trouble in the future when poppler internals change - the glib functions will remain constant.
So, are we correctly using the right functions and have the wrong dependency or we're not using the right functions?
--Ted
participants (6)
-
Jeff Kowalczyk -
Jon A. Cruz -
Joshua Facemyer -
Joshua Facemyer / Impressus Art -
Miklós Erdélyi -
Ted Gould