On 01.02.19 14:09, Alexander Kobel wrote:
Hi,On 01.02.19 13:51, Knut Petersen wrote:On 31.01.19 16:04, Alexander Kobel wrote:is there an libopenjpeg1-devel package installed? If not: try to install and rerun gub ...and I can cleanly compile the recent poppler 0.73 with openjpeg2 backend from source, with a simple cmake + make.yes and no - Arch follows the principle that the packages provide both runtimes and development requirements at the same time, so there is no separation as in, e.g., Debian. In particular, I have the headers on my system, and pkg-config is configured correctly:
Moreover, checking with poppler 0.49 as used in GUB, and loosely following the package build script for 0.49 from
https://git.archlinux.org/svntogit/packages.git/plain/trunk/PKGBUILD?h=packages/poppler&id=1626dc8989ffc95eab611e4bd47d54f9b0fcfde0 (nothing too fancy in Arch packaging, yay!), the build succeeds after ./configure <--enable-unrelated-stuff> --enable-libopenjpeg=openjpeg1 makeNote the absence of any paths, flags, etc. - everything is detected automagically:
Building poppler with support for:
font configuration: fontconfig
splash output: yes
cairo output: yes
qt4 wrapper: yes
qt5 wrapper: yes
glib wrapper: yes
introspection: yes
cpp wrapper: yes
use gtk-doc: no
use libjpeg: yes
use libpng: yes
use libtiff: yes
use zlib compress: yes
use zlib uncompress: no
use nss: yes
use libcurl: no
use libopenjpeg: yes
with openjpeg1
use cms: yes
with lcms2
command line utils: yes
Cheers,
Alex
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
