FIXINCLUDES(1)

πŸ“¦
version 26.08.2 Β· 2 versions
  • 26.08.2 Β· arch rolling, epel 10, epel 9, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0 (latest)
  • 26.04.2 Β· alpine 3.24
, in arch rolling, epel 10, epel 9, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0

πŸ’– fixincludes(1) β€” the girlies' guide to trimming your #includes πŸ’–

okay so bestie, this is the manual page for fixincludes, section 1 of the manual. yes, that section 1. we're in the big leagues now. sit down, grab a boba, and let's clean up your source files together πŸ§‹βœ¨


✨ NAME ✨

fixincludes β€” Reduce the number of #includes in KDE source files πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

fixincludes [-v, --verbose] [-e, --experimental] [-m, --modify] [file]
            [--help]

look at her. so simple. so elegant. she ate. πŸ”₯


🌸 DESCRIPTION 🌸

okay so here's the vibe: fixincludes tries to reduce the number of #includes in C++ source files. iconic behaviour, honestly. less clutter, more slay. πŸ’…

but real talk β€” much of its processing is specific to KDE sources, so it might not work so well with sources for non-KDE applications. she's a KDE girlie through and through, and she's not gonna pretend otherwise. no cap. πŸ™ˆ

so what problems does she spot? here's the list, bestie:

  • Including headers that are no longer supported but which exist for compatibility with older Qt/KDE versions πŸ‘€
  • Including the same file multiple times 😭 (girl. we talked about this.)

there's also an experimental mode which tries removing each #include one at a time (with a few exceptions) to see whether the source still compiles. ooh, spicy. 🌢️

⚠️ bestie, listen to me very carefully: this experimental mode will modify the original sources. it's not playing. it's not joking. it will touch your files. 🫢

by default though? the sources will not be modified. the identified problems will simply be written to standard output. so you can peek without committing. we love a low-stakes vibe check. ✨

now β€” which files are we even looking at? the list of C++ sources to examine should be given on the command-line. that's it, that's the rule. but if no files are given, all C++ sources in or beneath the current directory will be examined β€” with the exception of directories whose Makefile.am contains -UQT_NO_COMPAT or -UKDE_NO_COMPAT. she's thorough, but she knows where she's not wanted. 😌

and for the record: this utility is part of the KDE Software Development Kit. πŸ‘‘


πŸŽ€ OPTIONS πŸŽ€

  • -v, --verbose β€” Verbose mode, bestie. Additional debugging output is written to standard output. she's telling you everything she's thinking. main character energy, honestly. πŸ—£οΈβœ¨
  • -e, --experimental β€” Experimental mode, as described above in detail. and heads up: this option implies --modify. so like, yes, she will be touching your files. do not say we didn't warn you. πŸ’€
  • -m, --modify β€” As well as writing messages to standard output, actually modify the original sources to fix any problems that were found. committing to the bit. obsessed. πŸ’–

🌈 AUTHORS 🌈

fixincludes was written by Dirk Mueller <mueller@kde.org>. thank you for your service, king. πŸ‘‘


⭐ AUTHOR ⭐

Ben Burton <bab@debian.org>

  • Author. yes that's literally the whole description and honestly? valid. periodt. πŸ’…

and that's the whole page, bestie!! πŸŽ‰ this one came from the [FIXME: source] source and it's dated 2003-04-07 β€” an absolute vintage icon, truly ahead of her time. go forth, trim those includes, and remember: no duplicates, no outdated compat headers, no regrets πŸ’–βœ¨πŸ¦‹πŸŽ€

πŸ“¦ where this page comes from