FIND-ALL-SYMBOLS(1)

💖 find-all-symbols — the manual page, but make it slay 💖

okay bestie, gather round, because this is the manpage for find-all-symbols, and yes it's version 13, and yes we're gonna read the whole thing together like it's a group chat at 2am 🦋

---

✨ NAME ✨

find-all-symbols — it's the manual page for find-all-symbols 13, no cap 💅

---

🌸 DESCRIPTION 🌸

so the whole vibe is this, literally:

USAGE: find-all-symbols [options] <source0> [... <sourceN>]

and then, the OPTIONS, babes. buckle up 🎀

🌈 Generic Options (the basics, the starter pack, iykyk)

• --help — shows you all the available options. want even more? there's --help-hidden for that 👀
• --help-list — prints out a whole list of the available options. and yeah, there's a --help-list-hidden too if you're feeling nosy ✨
• --version — tells you the version of this program. iconic behaviour honestly 👑

💜 find_all_symbols options (the real main character energy)

• --extra-arg=<string> — an extra argument you want to append to the compiler command line 🫶
• --extra-arg-before=<string> — an extra argument you want to prepend to the compiler command line (yes, before, it goes first, it's giving line-leader) 💅
• --merge-dir=<string> — the directory for merging symbols 🧚
• --output-dir=<string> — the output directory where the results get saved 🍓
• -p=<string> — build path. that's it, that's the label, but bestie there's lore below ⬇️
  • -p <build-path> is used to read a compile command database.
  • for example, it can be a CMake build directory that has a file named compile_commands.json inside it. (use the -DCMAKE_EXPORT_COMPILE_COMMANDS=ON CMake option to get that output, mwah 💖)
  • when no build path is specified, a search for compile_commands.json will be attempted through all parent paths of the first input file.
  • see: https://clang.llvm.org/docs/HowToSetupToolingForLLVM.html for an example of setting up Clang Tooling on a source tree 🌈
• <source0> ... — here's where you specify the paths of your source files, okay? and listen, these paths are looked up in the compile command database. the rules, bestie, are specific:
  • if the path of a file is absolute, it needs to point into CMake's source tree.
  • if the path is relative, the current working directory needs to be in the CMake source tree, and the file must be in a subdirectory of the current working directory.
  • "./" prefixes in the relative files will be automatically removed, but the rest of a relative path must be a suffix of a path in the compile command database. so like, don't get cute with it 🙈
• More help text... — literally just that. more help text. that's all it says. 💀

---

okay real talk bestie: that's genuinely every single thing on the page. nothing skipped, nothing summarised, we read the whole menu and we ate 🔥

---

sign-off time 🫶 this was find-all-symbols 13, dated July 2023, and the source/version footer said FIND-ALL-SYMBOLS(1) on both sides, which is honestly such a symmetrical moment ✨ bye babes, go find those symbols 💖👑