Closed d closed 4 years ago
Thanks for the suggestion. Certainly cmake-format
should understand it's own listfiles ;). If you want to hack on it:
add_custom_command_tests.py
. It's a typical python unittest
. You can just add a test function with self.expect_format="""..."""
indicating the expected format. The base class will take care of the rest (don't worry about self.expect_parse in the existing test).But it's also a pretty trivial change and I'm happy to just add it to the next incremental release.
It was added in CMake 3.2 . It's frequently used when a project uses the Ninja generator because Ninja is quite particular about the exact "outcome" of each target / command.
I am willing to contribute, it seems I can fiddle with https://github.com/cheshirekow/cmake_format/blob/master/cmake_format/parse_funs/add_xxx.py . But I'll need a few pointers about what the coding conventions are, how to run tests locally, and how I should add tests.