If you like keyboard over mouse (which I do), mupdf is a nice alternative. Zoom is with + and - keys ( see http://manpages.ubuntu.com/manpages/natty/man1/mupdf.1.html ). ? brings up the help information for commands (which can be easy to forget with this program). It is a very minimal PDF viewer, but as I mentioned, performance (especially paging through large PDF files), is good. I've read that it also handles cbz file viewing, but haven't tried it yet.
When I built mupdf (which was a while ago before the openjpeg changes), I built all the libraries separately and let it to use the system libraries. From my notes, the steps for building mupdf were something like: Skip the configure step. make build=release make prefix=$DESTDIR build=release install DESTDIR=$DESTDIR Before building, I told it where the freetype include files and other related include files were: export XCFLAGS="-I/usr/local/include/freetype2 -I/usr/local/include/ $CFLAGS" If you're using /usr/include instead of /usr/local/include, change it to that or whatever directories are relevant on your system. I also have a note about adding any missing X libraries (-l options) it might not be able to find by exporting them with XLIBS environment variable. As to the .la files, I remove them during the build process. Haven't tried doing it afterwards in the /usr/lib directory. I'm sort of writing my own package manager that automates some of the build process. I build and install applications to DESTDIR and then package and create a tarball from them. Part of the packaging process is to do things like compress the man files (.gz) and another part is to eliminate any .la files under lib in DESTDIR. So far, haven't noticed any issues by doing so and it's actually resolved a few situations I was having when I wasn't doing this. From what I've read, the .la files are used at build time by libtool to figure out how to handle libraries. Since I'm building to DESTDIR, but installing someplace else, sometimes the .la files end up pointing to the wrong locations. Read that Debian and a couple of other distributions were removing their .la files and didn't have any issues doing so. Here were some of the references I ran across when I looked into adding this step to my build process: http://wiki.debian.org/ReleaseGoals/LAFileRemoval http://archives.gentoo.org/gentoo-dev-announce/msg_3fd5f34db7e0947ade0b08fbea0825da.xml Sincerely, Laura
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
