FIND-ALL-SYMBOLS(1)

💖 FIND-ALL-SYMBOLS(1) 💖

okay bestie, welcome to the manual page for find-all-symbols version 20 — yes that's the User Commands girlies, we're in terminal town now 💅

---

✨ NAME ✨

find-all-symbols — it's literally the manual page for find-all-symbols 20, no cap 🫶

---

🌸 DESCRIPTION 🌸

okay so the usage is giving:

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

and then it's just OPTIONS: underneath, like a little menu of everything you can do 🎀

---

🌈 Generic Options 🌈

the basic-girl options, the ones everybody knows:

• --help — shows you all the available options fr fr (and if you want the hidden ones too? --help-hidden, she's mysterious like that 🙈)
• --help-list — lists out the available options for you (same deal, --help-list-hidden exists if you want the secret menu 🔥)
• --version — shows you the version of this program, iconic behavior 👑

---

🦋 find_all_symbols options 🦋

this is the specific-to-this-tool section, the main character energy part:

• --extra-arg=<string> — an extra argument you tack onto the compiler command line (appended at the end, bestie)
• --extra-arg-before=<string> — same vibe but it goes before the compiler command line, prepend era ✨
• --merge-dir=<string> — the directory for merging symbols, that's the whole job 🧚
• --output-dir=<string> — the directory where the results get saved, your little output home 🍓
• -p <string> — build path 🏗️

---

💜 about -p <build-path> 💜

so -p <build-path> is the thing you use to read a compile command database, okay? let me break it down:

for example, it can totally be a CMake build directory where a file named compile_commands.json lives — and to get that output you use the -DCMAKE_EXPORT_COMPILE_COMMANDS=ON CMake option 🎀

and here's the tea: when you don't specify a build path at all, it will try to search for compile_commands.json by going through all the parent paths of the first input file 👀

if you want to see an example of setting up Clang Tooling on a source tree, the original points you here: https://clang.llvm.org/docs/HowToSetupToolingForLLVM.html 🫶

---

💅 about the source files 💅

<source0> ... — this is where you specify the paths of your source files. and ngl, these paths are looked up in the compile command database, so pay attention:

• if the path of a file is absolute, it needs to point into CMake's source tree 🎯
• if the path is relative, then 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. like, that's the rule, periodt 💀

---

More help text...

(that's literally what it says, bestie — the page just ends with that little teaser 🫠)

---

⭐ friendly reminder that all of this is exactly the facts, I'm just delivering them with ✨flavor✨ — no invented options, no extra lore, we keep it 100.

---

kisses, this was find-all-symbols 20, dated September 2026, and yes it's still wearing the FIND-ALL-SYMBOLS(1) fit 💖 🎀 slay, go read a manpage, ily 🫶