FIND-ALL-SYMBOLS(1)

💖 FIND-ALL-SYMBOLS 💖

okay bestie so this is find-all-symbols(1), a User Commands girly from the find-all-symbols manual, and yes we're doing this together, hand in hand, no cap. 🫶

---

✨ NAME ✨

find-all-symbols — literally the manual page for find-all-symbols version 19, she's an icon, she's a legend, and she is the moment. 👑

---

🌸 DESCRIPTION 🌸

so first thing, the usage, and it's giving:

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

like you hand her some options and then a whole pile of source files, source0 through sourceN, and she does her thing. periodt.

then, the options. let's go. 💅

---

🎀 OPTIONS 🎀

🌈 Generic Options

• --help — shows you all the available options. and if you want even more, there's --help-hidden for that. 🙈
• --help-list — displays a list of the available options. and again, --help-list-hidden exists if you're feeling extra and want more. ✨
• --version — displays the version of this program. she'll tell you who she is. 💁

🦋 find_all_symbols options

• --extra-arg=<string> — an additional argument that gets appended to the compiler command line.
• --extra-arg-before=<string> — an additional argument that gets prepended to the compiler command line. (prepend not append, she's specific about it, we respect that.)
• --merge-dir=<string> — the directory for merging symbols.
• --output-dir=<string> — the output directory for saving the results.
• -p <string> — build path. 👀

---

🧚 about -p <build-path>, bestie, listen

-p <build-path> is used to read a compile command database.

like for example, it can be a CMake build directory where a file named compile_commands.json exists. and to get that output you use the -DCMAKE_EXPORT_COMPILE_COMMANDS=ON CMake option. so cute of CMake.

when no build path is specified, a search for compile_commands.json will be attempted through all parent paths of the first input file. she goes looking, she's thorough. 🔍

see: https://clang.llvm.org/docs/HowToSetupToolingForLLVM.html for an example of setting up Clang Tooling on a source tree.

---

🌟 about <source0> ...

these specify the paths of source files. these paths are looked up in the compile command database.

• 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. don't skip that part, it matters. 💀

---

More help text...

(that's it, that's the whole line, she said "More help text..." and left it there. main character energy, honestly. 😭)

---

<div align="center">

sign-off time, bestie 🎀

this whole vibe was find-all-symbols 19, dated June 2025, and it came to you straight from FIND-ALL-SYMBOLS(1) in the User Commands section. love her, study her, use her responsibly. bye bestie, slay your build. 💖✨🌸🦋

</div>