FIND-ALL-SYMBOLS(1)

πŸ“¦
version 16.0.6 Β· 2 versions
, in debian bookworm

πŸ’– NAME πŸ’–

find-all-symbols β€” the manual page for find-all-symbols 16, bestie ✨


πŸŽ€ DESCRIPTION πŸŽ€

okay so basically, here's the vibe check πŸ‘‘

πŸ¦‹ USAGE πŸ¦‹

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

🌸 OPTIONS 🌸

✨ Generic Options ✨

  • --help β€” shows you the available options, periodt. (and if you add --help-hidden you get EVEN MORE πŸ‘€)
  • --help-list β€” prints a whole list of the available options. (again, --help-list-hidden exists if you're nosy like me πŸ™ˆ)
  • --version β€” tells you which version of this program you're running, no cap πŸ’…

πŸŽ€ find_all_symbols options πŸŽ€

  • --extra-arg=<string> β€” an extra argument that gets appended to the compiler command line ✨
  • --extra-arg-before=<string> β€” an extra argument that gets prepended to the compiler command line πŸ’œ
  • --merge-dir=<string> β€” the directory for merging symbols 🧚
  • --output-dir=<string> β€” the output directory where the results get saved πŸ“
  • -p <string> β€” build path 🫢

πŸ’« the -p build path thing πŸ’«

-p <build-path> is used to read a compile command database πŸ“š

like, for example, it can be a CMake build directory where a file called compile_commands.json lives (use the -DCMAKE_EXPORT_COMPILE_COMMANDS=ON CMake option to get that output). and when there's no build path specified, a search for compile_commands.json will be attempted through all the 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 ✨

🌈 the source files 🌈

<source0> ... β€” specify the paths of source files. these paths are looked up in the compile command database πŸ’–

and like, here's the tea:

  • 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 πŸ’…

⭐ More help text... ⭐

More help text...


not me writing a whole manpage and still saying "More help text..." β€” iconic, honestly πŸ’€

mwah, this was find-all-symbols 16, dated October 2023 β€” bye bestie, go slay some symbols πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from