MIG(1)

πŸ“¦ version 138, in nixpkgs unstable

πŸ’… mig β€” Mach Interface Generator πŸ’…

okay bestie, welcome to MIG(1) β€” the manual page for the one and only mig. lowkey iconic, fr fr.


✨ NAME ✨

mig β€” Mach Interface Generator. that's the name, no cap 🫢


🌸 SYNOPSIS 🌸

mig [ option ...  ] file

πŸ’… DESCRIPTION πŸ’…

okay so the mig command invokes the Mach Interface Generator, and its whole main-character job is generating Remote Procedure Call (RPC) code for client-server style Mach IPC from specification files. slay πŸ’–


πŸŽ€ OPTIONS πŸŽ€

  • -q / -Q β€” omit / emit warning messages. -q is the quiet one, -Q says speak up bestie πŸ—£οΈ
  • -v / -V β€” verbose mode (on / off) will summarize types and routines as they are processed. -v turns the yapping on, -V turns it off ✨
  • -l / -L β€” controls (off / on) whether or not generated code logs RPC events to system logs. -l is off, -L is on πŸͺ΅
  • -k / -K β€” controls (on / off) whether generated code complies with ANSI C standards. -k is on, -K is off πŸ’…
  • -s / -S β€” controls (on / off) whether generated server-side code includes a generated symbol table. -s is on, -S is off 🧾
  • -b / -B β€” controls (on / off) whether generated code includes bounds-checking annotations, such as __counted_by. -b is on, -B is off πŸ›‘οΈ
  • -i prefix β€” specify User file prefix. yes, capital-U User, keep it cute πŸ’–
  • -user path β€” specify name of user-side RPC generated source file.
  • -server path β€” specify name of server-side RPC generated source file.
  • -header path β€” specify name of user-side generated header file.
  • -sheader path β€” specify name of server-side generated header file.
  • -iheader path β€” specify internal header file name.
  • -dheader path β€” specify defines generated header file.
  • -maxonstack value β€” specify maximum size of message on stack.
  • -split β€” use split headers. periodt βœ‚οΈ
  • -arch arch β€” specify machine architecture for target code.
  • -MD β€” option is passed to the C compiler for dependency generation.
  • -cpp β€” this option is ignored. not me getting ignored at the function πŸ’€
  • -cc path β€” specify pathname to specific C compiler to use as the preprocessor.
  • -migcom path β€” specify pathname to specific migcom compiler to use for source code generation.
  • -isysroot path β€” specify SDK root directory.

and bestie, heads up: additional options provided are passed along to the C compiler unchanged. no edits, no vibe check, just straight through 🌈


mwah πŸ’‹ this iconic page is brought to you by Apple Computer, Inc., from the General Commands Manual, dated Nov 20, 2009 β€” go off and read those specs, bestie 🌸✨

πŸ“¦ where this page comes from