[poppler] Question about building Poppler trunk or latest release

[Marc J. Driftmeyer]

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:

> -rwxr-xr-x 1 root staff  2.5M Jan 17 11:02 libpoppler.so.19.0.0
> lrwxrwxrwx 1 root staff    20 Jan 17 11:02 libpoppler.so.19 -> 
> libpoppler.so.19.0.0
> lrwxrwxrwx 1 root staff    20 Jan 17 11:02 libpoppler.so -> 
> libpoppler.so.19.0.0
> -rwxr-xr-x 1 root staff  1.1K Jan 17 11:02 libpoppler.la
> -rw-r--r-- 1 root staff  3.3M Jan 17 11:02 libpoppler.a
> -rwxr-xr-x 1 root staff  339K Jan 17 11:02 libpoppler-glib.so.8.2.0
> lrwxrwxrwx 1 root staff    24 Jan 17 11:02 libpoppler-glib.so.8 -> 
> libpoppler-glib.so.8.2.0
> lrwxrwxrwx 1 root staff    24 Jan 17 11:02 libpoppler-glib.so -> 
> libpoppler-glib.so.8.2.0
> -rwxr-xr-x 1 root staff  1.2K Jan 17 11:02 libpoppler-glib.la
> -rw-r--r-- 1 root staff  410K Jan 17 11:02 libpoppler-glib.a
> drwxr-sr-x 2 root staff  4.0K Jan 17 11:02 girepository-1.0
> -rwxr-xr-x 1 root staff  487K Jan 17 11:02 libpoppler-qt4.so.3.7.0
> lrwxrwxrwx 1 root staff    23 Jan 17 11:02 libpoppler-qt4.so.3 -> 
> libpoppler-qt4.so.3.7.0
> lrwxrwxrwx 1 root staff    23 Jan 17 11:02 libpoppler-qt4.so -> 
> libpoppler-qt4.so.3.7.0
> -rwxr-xr-x 1 root staff  1.2K Jan 17 11:02 libpoppler-qt4.la
> -rw-r--r-- 1 root staff  670K Jan 17 11:02 libpoppler-qt4.a
> drwxr-sr-x 2 root staff  4.0K Jan 17 11:02 pkgconfig
> -rwxr-xr-x 1 root staff  100K Jan 17 11:02 libpoppler-cpp.so.0.2.0
> lrwxrwxrwx 1 root staff    23 Jan 17 11:02 libpoppler-cpp.so.0 -> 
> libpoppler-cpp.so.0.2.0
> lrwxrwxrwx 1 root staff    23 Jan 17 11:02 libpoppler-cpp.so -> 
> libpoppler-cpp.so.0.2.0
> -rwxr-xr-x 1 root staff  1.2K Jan 17 11:02 libpoppler-cpp.la
> -rw-r--r-- 1 root staff  123K Jan 17 11:02 libpoppler-cpp.a

/usr/local/lib/pkgconfig includes:

> -rw-r--r-- 1 root staff 222 Jan 17 11:02 poppler-splash.pc
> -rw-r--r-- 1 root staff 283 Jan 17 11:02 poppler-qt4.pc
> -rw-r--r-- 1 root staff 222 Jan 17 11:02 poppler.pc
> -rw-r--r-- 1 root staff 338 Jan 17 11:02 poppler-glib.pc
> -rw-r--r-- 1 root staff 304 Jan 17 11:02 poppler-cpp.pc
> -rw-r--r-- 1 root staff 236 Jan 17 11:02 poppler-cairo.pc

Default headers include:

/usr/local/include/poppler

/cpp, /glib and /qt4

Of course /poppler is completely empty.

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?

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

-- 
Marc J. Driftmeyer
Email :: mjd at reanimality.com <mailto:mjd at reanimality.com>
Web :: http://www.reanimality.com
Cell :: (509) 435-5212
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mjd.vcf
Type: text/x-vcard
Size: 316 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/poppler/attachments/20120117/bc062980/attachment.vcf>