Skip to content

🌱 Expose Meson runner program - #859

Open
Firat17aze wants to merge 1 commit into
ThrowTheSwitch:masterfrom
Firat17aze:expose-meson-runner-program
Open

Firat17aze wants to merge 1 commit into
ThrowTheSwitch:masterfrom
Firat17aze:expose-meson-runner-program

Conversation

@Firat17aze

Copy link
Copy Markdown

🍍

Fixes #835.

Meson consumers can currently retrieve Unity's gen_test_runner object, but that generator fixes the output pattern. This prevents consumers that need a custom output name or a fully controlled command line from using the bundled runner script directly.

This exposes the same discovered program as gen_test_runner_exe while leaving gen_test_runner unchanged. The Meson guide now shows how to use the program in a custom_target(), and the change log records the new subproject interface.

Validation:

  • rake ci — 3,070 tests passed with 0 failures; RuboCop checked 12 files with no offenses.
  • A standalone Meson consumer retrieved gen_test_runner_exe, generated a custom-named runner, compiled it with Unity, and passed its test (1/1).
  • git diff --check passed.

No hardware validation was needed because this change is limited to the host-side Meson integration.

LLMs were used for review and code generation in some parts of this pull request.

Meson consumers could only use the fixed generator object. That prevented
custom targets from choosing their own output name and full command line.

Expose the already-discovered runner as a subproject variable and document
direct custom-target usage. A downstream Meson consumer built and passed
with the custom runner output.

Resolves: ThrowTheSwitch#835
Signed-off-by: Firat17aze <your@email.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Expose generate_test_runner.rb as program from meson build file

1 participant