[qhull] Disable tools install on iOS

[DDoS]

CMake doesn't generate usable tool executables when cross-compiling to iOS, and the install step is broken due to invalid paths in the targets file.

• What does your PR fix?

  Skip installing the iOS tools, they don't run and there's no real use for them anyway.

• Which triplets are supported/not supported? Have you updated the CI baseline?

  all

• Does your PR follow the maintainer guide?

  yes

• If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?

  yes

[dg0yt]

There is #27260.

[DDoS]

There is #27260.

Yeah that's a cleaner solution, but it's waiting on upstream, and who knows when the next Qhull version will be released.
I think this issue is better for patching the iOS build while we wait for an upstream fix.

[dg0yt]

TBH I don't why the other PR is requested to wait. Of couse that patch could be minimized, without the formatting changes.

[BillyONeal]

TBH I don't why the other PR is requested to wait. Of couse that patch could be minimized, without the formatting changes.

We aren't qhull, we are a packaging solution, so we don't want to speak for them. Some patch principles:

• We prefer an official upstream release with the changes.
• We want to avoid patches that:
  • upstream would disagree with
  • cause vulnerabilities or crashes
  • we are incapable of maintaining across upstream version updates
  • are large enough to cause license entanglement with the vcpkg repository itself

That PR adds a new deployment scheme / knob, so we believe upstream needs an opportunity to weigh in. It's a build system feature and not a product feature, we're willing to take the patch if they don't respond.

[DDoS]

@BillyONeal Considering that #27386 says

We will skip this waiting period if we have high confidence that the change is correct. Examples of high confidence patches include, but are not limited to:
[...]

• Disabling irrelevant-in-vcpkg components of the build such as tests or examples.

Does this PR actually need to wait on upstream? The tools are irrelevant on iOS. There is #27260 that can supersede this if upstream agrees to take in changes to disable the tools build. This is only avoids installing them to avoid a bug at the last moment possible.

[BillyONeal]

There is #27260.

Yeah that's a cleaner solution, but it's waiting on upstream, and who knows when the next Qhull version will be released. I think this issue is better for patching the iOS build while we wait for an upstream fix.

That has been merged. Do you still want this change?

[DDoS]

There is #27260.

Yeah that's a cleaner solution, but it's waiting on upstream, and who knows when the next Qhull version will be released. I think this issue is better for patching the iOS build while we wait for an upstream fix.

That has been merged. Do you still want this change?

No real need for this PR with the other one merged.