DEPINFO(1)

📦 version 1010.6, in nixpkgs unstable

💖 NAME 💖

okay so bestie, gather round — depinfo is literally the Xcode dependency info file utility. that's the whole vibe. 🎀

✨ SYNOPSIS ✨

depinfo file ...

like, you just hand it one or more *file*s and it does its thing, no cap. 🫶

🦋 DESCRIPTION 🦋

so the depinfo utility is here to display the contents of Xcode Dependency Info files — and those files are made by the ld(1) and libtool(1) tools. that's it, that's the whole job, and honestly? it ate. 💅✨

🌸 XCODE DEPENDENCY INFO FILES 🌸

okay this is the part where it gets kinda iconic. the Xcode Dependency Info file format is a series of variable length records. and every single record? it begins with a single byte — an opcode — that tells you what type of record you're looking at. 👑

so the opcodes are followed by a single null-terminated C string, and what's inside that C string depends on the opcode. usually it's an absolute path to a location on disk. iykyk. 🦋

the opcodes include:

  • 0x00 — Tool — a string describing the tool that produced the dependency information. fr fr, the content and format of this string will vary between tools, so don't come for it. 🙈
  • 0x10 — Input Found — an absolute path to an existing file that was used, directly or indirectly, to build the output file. she's real, she's there, she's serving input energy. 💜
  • 0x11 — Input Missing</em> — an absolute path to a file on disk that was looked for but not found. lowkey sad. if a file had been found at that location, it would have been used as input. 😭
  • 0x40 — Output — an absolute path to the file generated by the tool. the main character, the final product, the moment. 🔥👑

🎀 SEE ALSO 🎀

go read those too bestie, they're the whole reason this file format even exists. 🌈⭐

and that's the page!! Darwin, dated September 10, 2019, living in DEPINFO(1) — periodt. 💅💖 mwah, go read some dependency info files, ily 🫶✨

📦 where this page comes from