-
Notifications
You must be signed in to change notification settings - Fork 603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUILD] Build fails when enabling libjxl support #4558
Comments
Do you know what version of libjxl is being found/used? |
Never mind, I see you posted it. Sorry. |
Checking the JxlEncoderAllowExpertOptions() now. Will dig deeper tomorrow. |
The INSTALL.md does not mention libjxl, that was an oversight and should be added. externalpackages.cmake implies that the minimum is libjxl 0.10.1. The report above indicates v0.11.1 is being used. So maybe our minimum is too low? Or is the 0.11.1 too new -- i.e., changes have occurred recently that are incompatible with what we have, and we need adjustment on our end? Those two choices are among the first things I'd recommend double-checking. |
This 0.11.1 is hot. So API/ABI impedance mismatch. |
Oh, I see, just released this past week! So probably we just need to make adjustments on our end to accommodate recent changes on the libjxl side. |
We don't have a lot of historical experience with libjxl, so I don't know how frequently it's likely to break its APIs. But if we think breaking changes might be common for libjxl, it may be another library that we wish to build from scratch as part of our "bleeding edge" CI test, so that we can see any incompatibilities coming long before they are a tagged version. |
(The "bleeding edge" test is one corner of our CI where we build main/master top-of-tree of several key dependencies, to catch problems before they make releases.) |
Beware the libjxl build is quite a long process. So this should be made optional, and probably off by default. So, YMMV. |
Aha, understood. I was just speculating. The libraries we build from scratch for bleeding edge are chosen based on some balance of their degree of criticality, how likely they are to break compatibility, and the time and effort to build them. So maybe libtiff or OpenEXR are both highly critical and worth the relatively low expense to build, but possibly libjxl won't strike the right balance. I mainly just wanted you to know that this is an option if it seems worth it. |
I'm trying to build OpenImageIO 3.0.1.0 with libjxl support, but the build fails with the following error:
I had the same error when building OIIO 3.0.0.3
I'm using libjxl v0.11.1
GCC: 11.4.1
cmake: 3.27.8
OS: Rocky Linux 9.4
There's no mention of a supported version of libxl in the installation instruction, so maybe the issue is that the version I'm using is not supported?
Thanks for your help in advance,
Cheers
The text was updated successfully, but these errors were encountered: