alois31
21fc0ddce5
Currently, a bunch of documentation is generated by embedding parts of it in
the nix executable, getting it out again by running it, and then postprocessing
the output. This is bad, since it creates a pointless dependency of the
documentation on the executable, and also makes documentation generation
impossible when cross-compiling.
Instead, both the code and the documentation should be generated from data, see
#292 . Here we start applying
this approach to the experimental and deprecated features, which are done in
one go since the technical implementation is very similar.
Of course, the actual benefits are not realised yet, since the offending
pattern is used in several more places. These will be fixed later.
Change-Id: I4c802052cc7e865c61119a34b8f1063c4decc9cb
23 lines
884 B
Python
Executable file
23 lines
884 B
Python
Executable file
#!/usr/bin/env python3
|
|
import subprocess
|
|
|
|
def get_targets_of_rule(build_root: str, rule_name: str) -> list[str]:
|
|
return subprocess.check_output(['ninja', '-C', build_root, '-t', 'targets', 'rule', rule_name]).decode().strip().splitlines()
|
|
|
|
def ninja_build(build_root: str, targets: list[str]):
|
|
subprocess.check_call(['ninja', '-C', build_root, '--', *targets])
|
|
|
|
def main():
|
|
import argparse
|
|
ap = argparse.ArgumentParser(description='Builds required targets for clang-tidy')
|
|
ap.add_argument('build_root', help='Ninja build root', type=str)
|
|
|
|
args = ap.parse_args()
|
|
|
|
targets = [t for t in get_targets_of_rule(args.build_root, 'CUSTOM_COMMAND') if t.endswith('.gen.hh')]
|
|
targets += [t for t in get_targets_of_rule(args.build_root, 'CUSTOM_COMMAND') if t.endswith('.gen.inc')]
|
|
ninja_build(args.build_root, targets)
|
|
|
|
if __name__ == '__main__':
|
|
main()
|