libtree(1)

✨ libtree — print shared object dependencies as a tree ✨

okay bestie, so libtree is a thing in the User Manuals section of the manual (section 1, obviously 💅), and it does exactly what it says on the tin: it shows you the shared libraries your programs need, but as a tree. iconic behaviour honestly 🎀

🌸 SYNOPSIS 🌸

libtree [ option ]... [--] [ file ]...

🦋 DESCRIPTION 🦋

So here's the tea 🍓: libtree prints the shared libraries that each program or shared library on the command line needs, and it lays them out like a tree so you can actually see the structure instead of squinting at a wall of paths. main character energy fr fr 👑

And by default? It hides certain common system libraries to prune the tree — so you're not drowning in noise you didn't ask for. lowkey thoughtful of it 🫶

💅 OPTIONS 💅

• -h, --help — prints usage. you know the drill, bestie ✨
• --version — prints version info 📌
• -p, --path — shows the path of libraries instead of their soname
• -v — shows the libraries that get skipped by default (the hidden ones! sneak peek 👀)
• -vv — shows the dependencies of those libraries that get skipped by default
• -vvv — shows the dependencies of libraries you've already encountered
• --ldconf arg — path to a custom ld.so.conf or ld-elf.so.conf file
• --max-depth n — limits library traversal to a depth of at most n. > ⚠️ heads up: this value cannot be larger than 32. it's a hard cap, no negotiating 💀
• -- — every argument after -- is treated as a path, not a flag. so if your filename is being dramatic and looks like an option, this is your escape hatch 🚪

🌈 ENVIRONMENT 🌈

LD_LIBRARY_PATH can be used to provide additional search paths. extra places to look, extra chances to find your libs 🧚

👑 AUTHOR 👑

Harmen Stoppels <me@harmenstoppels.nl> — legend behaviour honestly 💜

🔥 SEE ALSO 🔥

• ldd(1)

okay that's the whole page, no cap. this was libtree(1), the Linux one, dated 2020-04-13 — go forth and inspect your dependencies, bestie, you've absolutely got this 💖✨🎀