[poppler] Question about building Poppler trunk or latest release

Albert Astals Cid aacid at kde.org
Tue Jan 17 13:29:29 PST 2012

El Dimarts, 17 de gener de 2012, a les 13:02:40, Marc J. Driftmeyer va 
> To all that this concerns,
> I have a question to missing header files that don't install, by
> default, making poppler not very useful to build applications like Scribus.
> Whether I use cmake or the traditional autotools and configure the path
> for /usr/local or some other path like /opt the question isn't that the
> package doesn't compile or install it's just that it doesn't install
> enough parts to make it useful for building other packages.
> Debian clearly has a custom script to include the `extras' the default
> install fails to add.
> The default install includes:
> ...
> To get Scribus trunk to build I have to include under /poppler the
> following:
> /fofi, /splash and /goo
> I also have to include [as Debian does] all the header [.h] files under
> the /poppler source
> Finally, I have to include the poppler-config.h that is autocreated
> during the build process of poppler under the build path of /poppler
> QUESTION: Is this by design so that the package maintainers can come up
> with their own custom install scripts or is this an oversight?

It is by design, read ./configure --help if you want to install more headers


> I ask this as Scribus clearly builds with the assumptions that Debian
> has made in it's package maintenance and installation process.
> Sincerely Yours,
> Marc

More information about the poppler mailing list