libjxl: migrate to Conan v2, add v0.10.2

[valgur]

.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[HappySeaFox]

Hi, any progress?

[HappySeaFox]

Bump! Is it ready for merging?

[valgur]

@uilianries @RubenRBS @franramirez688 pinging for a review, in case you have missed this one

[valgur]

#24165

[Julianiolo]

@valgur What does this mean? Is this closed because you are also quitting cci? Forgive me as a I am somewhat confused :)

[conan-center-bot]

Conan v1 pipeline ✔️

All green in build 4 (3b427b227b4e22c699276112923987488a35398e):

• libjxl/0.6.1:
  All packages built successfully! (All logs)

• libjxl/0.8.2:
  All packages built successfully! (All logs)

• libjxl/0.10.2:
  All packages built successfully! (All logs)

---

Conan v2 pipeline ✔️

Note: Conan v2 builds are now mandatory. Please read our discussion about it.

All green in build 6 (3b427b227b4e22c699276112923987488a35398e):

• libjxl/0.10.2:
  All packages built successfully! (All logs)

• libjxl/0.8.2:
  All packages built successfully! (All logs)

• libjxl/0.6.1:
  All packages built successfully! (All logs)

[uilianries]

Built locally, looks okay.

[Cyriuz]

Sorry for reviving this but I just got a surprise when updating this package with allocator mismatches due to this change in my static build and I just wanted to ask; Should we really do this here? From the linked cmake I gather that libjxl tries to use tcmalloc by default if it exists, but if we don't add it as a dependency, it shouldn't exists unless it is available on the system? Which I assume is a common problem in general with many libs. Could a better solution be to be able to disable it completely upstream instead either via a patch or a PR to them?

[valgur]

Thanks for reporting this. Please open it as a separate issue for more visibility.

[Cyriuz]

Sure, added one #26707