Package Base Details: libjxl-git

Git Clone URL: https://aur.archlinux.org/libjxl-git.git (read-only, click to copy)
Keywords: jpeg-xl
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 14
Popularity: 0.000008
First Submitted: 2021-06-02 18:30 (UTC)
Last Updated: 2024-03-01 15:40 (UTC)

Latest Comments

1 2 3 4 5 6 .. 13 Next › Last »

dbermond commented on 2024-07-14 23:16 (UTC)

@yota the pixbuf loader is installed by the build system. So, if you think something is wrong with the pixbuf install location, maybe you should report it upstream. By my knowledge, it is installing to the right place. Can you please specifically point what you think is wrong?

dbermond commented on 2024-07-14 23:11 (UTC)

@xiota I told you it does not work. Since now there is a separated repository, I have created the package jpegli-git in the AUR.

yota commented on 2024-07-14 11:56 (UTC) (edited on 2024-07-14 11:56 (UTC) by yota)

the plugins are compiled by this pkgbuild (-DJPEGXL_ENABLE_PLUGINS=true) but I struggle to check that the gdk-pixbuf is correctly installed as specified here : https://github.com/libjxl/libjxl/tree/main/plugins/gdk-pixbuf

is it the case ?

dbermond commented on 2024-04-14 15:27 (UTC)

@xiota What I mean, is that your package have the great potential to break the system of users that have libjpeg (libjpeg-turbo) installed, hence it's broken. I understand that it should not be used in the way you propose. My pointed comment explains why, as this subject have already been talked before.

dbermond commented on 2024-04-10 16:58 (UTC)

@xiota Your libjpegli package is broken, as it cannot be treated as a provider for libjpeg. Please read my previous comment from 2023-08-12 about libjpegli.

louietaur commented on 2024-03-04 11:05 (UTC) (edited on 2024-03-04 11:06 (UTC) by louietaur)

@0ion9 I encountered a similar issue with building the package and not being able to find org.jpeg.jpegxl.jar. I fixed it by running archlinux-java status and selecting a JDK instead of JRE as my default Java enviroment.

Apparently, I had set java-8-openjdk/jre as default for some reason instead of java-21-openjdk. The package probably wasn't building right because it needed a JDK, not a JRE.

I remember running into this issue before and not being able to figure it out. Checking CMakeCache.txt led me to find that some tools like javac were not being found, hence the JNI jar not being built.

dbermond commented on 2023-10-09 02:03 (UTC)

@0ion9 If it builds in a clean chroot with devtools but does not build locally with makepkg, then something is wrong with your system. Up to you to find out. As I said since the beginning, the package is building fine and there is no issue.

1 2 3 4 5 6 .. 13 Next › Last »