qhull: add libqhullcpp component, add v8.1-alpha4

[valgur]

Summary

Changes to recipe: qhull/cci.20231130

Motivation

The qhull recipe currently does not export the libqhullcpp component, which is required by:

• cilantro: cilantro: new recipe #24528
• Open3D: https://github.com/isl-org/Open3D

I also added the latest head commit version to the recipe, since the development version includes a few useful changes, such as qhull/qhull#76 (thanks, @SpaceIm!).

Dropped v8.0.0, which is redundant to v8.0.1 and not used in any recipes.

Details

The cpp component is only available with the newly added version since I did not want to modify the existing patches.

Like the reentrant option, the cpp component is always built, but only exposed in package_info() when the option is enabled.

I had to re-enable the building and installing of the non-reentrant shared C library for backwards compatibility in the latest version.

• Resolves [question] Why is libqhullcpp excluded from all qhull packages? #16321
• Resolves [request] qhull/8.0.2 #13955 (presumably)

---

• Read the contributing guidelines
• Checked that this PR is not a duplicate: list of PRs by recipe
• Tested locally with at least one configuration using a recent version of Conan

[valgur]

cilantro builds fine locally with an unvendored libqhullcpp library after these changes: valgur@b73a6bc

[SpaceIm]

Would it be possible to ask upstream a release in order to avoid a custom cci version?

[AbrilRBS]

Would it be possible to ask upstream a release in order to avoid a custom cci version?

This would be ideal @SpaceIm @valgur :)

[conan-center-bot]

Conan v1 pipeline ✔️

All green in build 6 (36811bf6d67682aa7b527634e6479adccaf456b4):

• qhull/7.3.2:
  All packages built successfully! (All logs)

• qhull/8.1-alpha4:
  All packages built successfully! (All logs)

• qhull/8.0.1:
  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 (36811bf6d67682aa7b527634e6479adccaf456b4):

• qhull/8.0.1:
  All packages built successfully! (All logs)

• qhull/7.3.2:
  All packages built successfully! (All logs)

• qhull/8.1-alpha4:
  All packages built successfully! (All logs)

[perseoGI]

Would it be possible to ask upstream a release in order to avoid a custom cci version?

@valgur @SpaceIm did you have some time to request for a semantic release schema at upstream? https://github.com/qhull/qhull/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen

[valgur]

@perseoGI I asked and they kindly created a new pre-release: qhull/qhull#128 (comment)
I've already updated the recipe accordingly.

[shkwon98]

@jcar87 @uilianries @AbrilRBS
I'm really looking forward to it being merged...!

[perseoGI]

I've just launched the new CI for this PR. Once CI is green, I'll review! 🐸

[shkwon98]

@perseoGI
Is there any progress?