Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Remove USE_EXTERNAL_CLI11: it downloads CLI11 2.3.2 while the vendored header is 2.5.0

Open Beginner friendly
  • Is something wrong?
#175 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
cmake, cpp
Domain
build-system

Research direction

Read the USE_EXTERNAL_CLI11 option and conditional block in CMakeLists.txt, then inspect cmake/CLI11.cmake and references found with the two git grep commands in the issue. Remove the option and module, then run the listed build, ctest, and format check commands. Done means the vendored CLI11 header is used and no references to the option or module remain.

Written by the indexing model from the issue text.

Description

build good first issue severity/minor

ctrace parses its command line with the CLI11 header vendored in external/CLI11.hpp, version 2.5.0. With -DUSE_EXTERNAL_CLI11=ON (CMakeLists.txt:115-120), CMake downloads CLI11 v2.3.2 instead (cmake/CLI11.cmake): an older version that CI never builds, while the release license check reads the vendored header (CMakeLists.txt:209-214). The option gives two possible versions of the same dependency, and nothing needs it.

To do: remove the option and keep the vendored header.

How:

  • delete cmake/CLI11.cmake;
  • delete the USE_EXTERNAL_CLI11 option and its if block in CMakeLists.txt (lines 115 to 120);
  • run git grep -n USE_EXTERNAL_CLI11 and git grep -n CLI11.cmake to check that nothing else refers to them.

The wiki's build page also lists the option; a maintainer will update it.

Check:

cmake --build build --parallel 4
ctest --test-dir build --output-on-failure
./scripts/format-check.sh

Acceptance

  • cmake/CLI11.cmake is gone, and git grep USE_EXTERNAL_CLI11 finds nothing.
  • The README build configures and builds, and ctest passes.

From the technical debt register (docs/quality/technical-debt.md, D8).

Dominant language
C++
Stars
5
Forks
4
Avg merge
1h 9m
Merged PRs (30d)
81

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CoreTrace/coretrace

All issues in CoreTrace/coretrace

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.