Enhance meson support so that it can automatically generate a test runner#551
Merged
mvandervoord merged 2 commits intoThrowTheSwitch:masterfrom Feb 6, 2023
Conversation
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current
meson.buildfile is all that's needed to link Unity into a parent project. However, this doesn't expose any of the helper scripts, withgenerate_test_runner.rbbeing one of the most important for "it just works" testing.The added generator makes it easy to call
generate_test_runner.rbwith given input and output files, allowing Meson to automatically integrate the runner into its build environment. This did require makinggenerate_test_runner.rbexecutable and adding a#!though.The approach used is the best I can find from scouring the docs. From a brief discussion with a Meson dev, the path should magically do the right thing. Alas it doesn't and likely I'll need to file a bug. This works in the meantime however.
I've added some documentation in
docs/- happy to refine as needed :)