Package Details: llpp-git 26b.r9.g1415638-1

Git Clone URL: https://aur.archlinux.org/llpp-git.git (read-only)
Package Base: llpp-git
Description: A graphical PDF viewer which aims to superficially resemble less(1).
Upstream URL: http://repo.or.cz/w/llpp.git
Licenses: custom
Conflicts: llpp
Provides: llpp
Submitter: mfwitten
Maintainer: aksr
Last Packager: aksr
Votes: 60
Popularity: 0.005208
First Submitted: 2010-10-26 22:21
Last Updated: 2017-04-12 08:15

Dependencies (35)

Required by (0)

Sources (1)

Latest Comments

kngwyu commented on 2017-11-02 14:36

@respiranto
Original source looks like modified with this commit in mupdf,
http://git.ghostscript.com/?p=mupdf.git;a=commitdiff;h=626ea2ea771735492c9a4350ae02b26ea09d1423, but Arch's mupdf is still version 1.11 released in April this year.
I think this is the cause of the compile error.

respiranto commented on 2017-10-29 20:12

Fails to build again [0].

[0] https://respiranto.de/data/llpp-git.err

hero commented on 2017-04-11 21:16

libmupdf version 1.11 just came out. With that version the current head compiles again. This is what I did to make it compile: http://sprunge.us/aIMj I do not know if other modifications make it even better, but it might be a starting point for you to update the package.

Cheers

menta commented on 2016-12-15 18:14

Here is an updated PKGBUILD: http://pastebin.com/ZXhPAFz7

It contains new dependencies and optional dependencies, modifications to avoid build errors, and new packaging instructions.

A note about (optional) dependencies: file, gzip, and bzip2 are members of the base group, which is assumed to be installed on all Arch Linux systems, so these packages shouldn't be listed in the *depends arrays:
https://wiki.archlinux.org/index.php/makepkg#Usage

drrossum commented on 2016-07-06 07:09

The newest llpp revisions seem to be incompatible with the current mupdf library. The llpp package does still work.

loserMcloser commented on 2016-07-05 16:39

Build fails, I guess mupdf package removed include files?

+ ocamlc.opt -ccopt '-I /usr/include/freetype2 -Wextra -Wall -Werror -D_GNU_SOURCE -O -g -std=c99 -pedantic-errors -Wunused-parameter -Wsign-compare -Wshadow -o build//link.o' -c ./link.c
./link.c:43:24: fatal error: mupdf/fitz.h: No such file or directory
#include <mupdf/fitz.h>

jooch commented on 2016-01-30 00:50

Unable to build this:

+ ocamlc.opt -ccopt '-I /usr/include/freetype2 -Wextra -Wall -Werror -D_GNU_SOURCE -O -g -std=c99 -pedantic-errors -Wunused-parameter -Wsign-compare -Wshadow -o build//link.o' -c ./link.c
./link.c:198:5: fout: unknown type name ‘fz_stext_page’
fz_stext_page *text;

tutu commented on 2016-01-12 02:42

Hi drrossum - Thanks for getting back to me. I agree with you about the haskell dependency, no need to include while not necessary.

I tried the package build and it works if mupdf-git is installed, and it does not when mupdf is installed instead. I think this is expected till the maintainer of mupdf release a new version.

Thanks for the help. Hopefully other people interested in llpp-git will be able to do it now.

drrossum commented on 2016-01-11 17:29

Hi tutu,
Thank you for the helpful comments on patching the build.sh script for the recent changes in mupdf libraries. I pushed an updated PKGBUILD that includes your patches.

I use haskell myself, but many users will not appreciate the large build dependency this would pull in. So I don't want to use it in the PKGBUILD.

I included openjpeg2 as explicit dependency so that we don't depend on the mupdf-git configuration for building llpp-git.

The newest PKGBUILD works for me, but please let me know if you run into issues.

tutu commented on 2016-01-10 04:16

Hi drrossum - Thanks for advising mupdf-git. I tried out the package and it seems to work. There is a caveat though, the developers of mupdf are not providing third-party libraries anymore. Now, besides libmupdf.a, they create another static lib (libmupdfthird.a) that contains the routines of the third-party libs (eg, libmujs, openjpeg, etc) that llpp utilizes.

The build script that llpp-git PKGBUILD uses (build.sh) was not synced by llpp developers, they only updated Shakefile.hs. I got in contact with llpp developer on Github and I was surprised how fast I got a reply. Now the build.sh script works if you clone the llpp and mupdf repositories the way they describe in BUILDING file (the easy way, as they say).

To build using PKGBUILD I had to change

sed -i -e 's+-lopenjpeg+-lopenjp2+' build.sh

to

sed -i -e 's+-lmupdfthird+-lmupdfthird -lz -lfreetype -ljpeg -ljbig2dec+' build.sh

When building mupdf, you can choose which third party libs will be build as a git submodule, linking them statically to libmupdfthird.a. In mupdf-git there are two third-party git submodules current being initialized, openjpeg and mujs, hence they did not being linked explicitly on the line above anymore.

I would like to ask some questions:

1. The way I changed the PKGBUILD file, I had to know which libraries were linked statically in mupdf. Is there anyway to know this with out looking the PKGBUILD of mupdf-git?

2. What is your opinion on Shakefile.hs vs build.sh?

3. Is it better to initialize all the git submodules and link the third-party libs statically to libmupdfthird.a?

Thanks again for your time and help.

All comments