Disable CLI11 vendoring by default

[scpeters]

🦟 Bug fix

Part of #135

Summary

CLI11 is available upstream, so don't vendor by default.

Checklist

• Signed all commits for DCO
• Added tests
• Updated documentation (as needed)
• Updated migration guide (as needed)
• Consider updating Python bindings (if the library has them)
• codecheck passed (See contributing)
• All tests passed (See test coverage)
• While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

[scpeters]

we may need to update the package metadata to ensure the cli11 dependency is installed properly in each platform. I don't see it in the gz-utils3 homebrew formula for example

[scpeters]

we may need to update the package metadata to ensure the cli11 dependency is installed properly in each platform. I don't see it in the gz-utils3 homebrew formula for example

it's missing from both noble and homebrew, though homebrew doesn't report cmake warnings so its build status looks fine

[scpeters]

we may need to update the package metadata to ensure the cli11 dependency is installed properly in each platform. I don't see it in the gz-utils3 homebrew formula for example

it's missing from both noble and homebrew, though homebrew doesn't report cmake warnings so its build status looks fine

updated metadata for homebrew in osrf/homebrew-simulation#2928 and Ubuntu in 6e8fead

the windows metadata still needs to be updated

[scpeters]

the windows metadata still needs to be updated

adding cli11 to list of vcpkg dependencies to install in gazebo-tooling/release-tools#1230

I'm not sure what to do for conda (cc @traversaro)

[traversaro]

I'm not sure what to do for conda (cc @traversaro)

At the conda-forge level, cli11 was already added as a dependency (and that was the reason why I added this option). For the gazebo internal conda-based Windows CI, I am not sure where dependencies are stored, perhaps @j-rivero may know more.

[traversaro]

For the gazebo internal conda-based Windows CI, I am not sure where dependencies are stored, perhaps @j-rivero may know more.

Perhaps we need to add cli11 in https://github.com/gazebo-tooling/release-tools/blob/master/conda/envs/legacy/pixi.toml and re-generated the pixi.lock ?

[j-rivero]

I've hijacked gazebo-tooling/release-tools#1230 to include the conda update.

[scpeters]

I've hijacked gazebo-tooling/release-tools#1230 to include the conda update.

thanks! I'll mark this ready for review once we've merged gazebo-tooling/release-tools#1230

[scpeters]

@osrf-jenkins run tests please

[scpeters]

@osrf-jenkins run tests please

[scpeters]

this is ready for review

[j-rivero]

Support is not found in Windows.

CMake Warning at C:/J/workspace/gz_utils-pr-cnlwin/ws/install/gz-cmake4/share/cmake/gz-cmake4/cmake4/GzFindPackage.cmake:201 (find_package):
  By not providing "FindCLI11.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "CLI11", but
  CMake did not find one.

  Could not find a package configuration file provided by "CLI11" with any of
  the following names:

    CLI11Config.cmake
    cli11-config.cmake

  Add the installation prefix of "CLI11" to CMAKE_PREFIX_PATH or set
  "CLI11_DIR" to a directory containing one of the above files.  If "CLI11"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  CMakeLists.txt:37 (gz_find_package)


-- Looking for CLI11 - not found

[scpeters]

Support is not found in Windows.

can you take a look at gazebo-tooling/release-tools#1307?

[j-rivero]

@osrf-jenkins run tests

[j-rivero]

working, thanks for the fix!

[scpeters]

I updated the migration guide in a4d96d6