IWYU_TOOL.PY(1)

✨ NAME ✨

iwyu_tool.py β€” the Include-what-you-use compilation database driver πŸ’–

(we're in the User Commands section btw, so you know this is the real-deal runnable girlie and not some library deep lore 🫢)


πŸŽ€ DESCRIPTION πŸŽ€

okay bestie so here's the vibe. You run it like this:

usage: iwyu_tool.py [-h] [-v] [-o {clang,iwyu}] [-j JOBS] -p
<build-path>

[source [source ...]] -- [<IWYU args>]
[source [source ...]]

and it is literally the Include-what-you-use compilation database driver. That's the whole job description. She drives the compilation database. Main character energy only πŸ’…

🌸 positional arguments 🌸

  • source β€” zero or more source files to run IWYU on. Zero!! As in, if you don't name any, she just defaults to all of them in the compilation database. Not me handing over the aux πŸŽ€

⭐ optional arguments ⭐

  • -h, --help β€” show this help message and exit. The classic. The icon. The "I forgot the flags again" savior πŸ™ˆ
  • -v, --verbose β€” print the IWYU commands. Yes queen, show your work, we love transparency ✨
  • -o {clang,iwyu}, --output-format {clang,iwyu} β€” output format, and the default is iwyu. Pick your fighter: clang or iwyu 🌈
  • -j JOBS, --jobs JOBS β€” number of concurrent subprocesses. Go parallel, go fast, go feral πŸ”₯
  • -p <build-path> β€” the compilation database path. This one's required, no cap, she will not guess where your build lives πŸ’€
also important: she assumes include-what-you-use is available on the PATH. So if it's not on your PATH, that's a you problem, not a her problem 😭 fix your PATH bestie.

that's it, that's the page β€” short, sweet, slays 🌸

this lil masterpiece is iwyu_tool.py version 6.0-2, dated September 2018 β€” an absolute vintage icon, and yes she still ate πŸ‘‘