Ccomp(3)

πŸ’… NAME πŸ’…

Ccomp β€” Compiling C files and building C libraries

okay so bestie, this is the Ccomp(3) page from the OCaml library manual, and it's literally about exactly that: compiling C files and building C libraries. The manual name is folded in right here near the top because we are not doing the copy-paste header line, periodt. πŸ’–

🧚 Module 🧚

Module Ccomp

That's the module, bestie β€” Ccomp, no cap.

✨ Documentation ✨

Module Ccomp : sig end

Compiling C files and building C libraries

⚠️ Warning: this module is unstable and part of Compiler_libs .

Now the actual goods, aka the vals, all copied exactly because we do not play with signatures:

  • val command : string -> int β€” takes a string and gives back an int. That's the whole signature on the page, bestie.
  • val run_command : string -> unit β€” takes a string and returns unit; clean, simple, signature-only.
  • val compile_file : ?output:string -> ?opt:string -> ?stable_name:string -> string -> int β€” three optional labeled args (?output:string, ?opt:string, ?stable_name:string), then a string, then an int. All right there, no guessing.
  • val create_archive : string -> string list -> int β€” string, string list, int. That's the lineup.
  • val quote_files : response_files:bool -> string list -> string β€” labeled response_files:bool, then string list, then string.
  • val quote_optfile : string option -> string β€” string option in, string out.

And then there's this icon of a type, exactly as written:

       type link_mode =
        | Exe
        | Dll
        | MainDll
        | Partial

The variants are Exe, Dll, MainDll, and Partial β€” all four, present and accounted for. πŸ’…

  • val call_linker : link_mode -> string -> string list -> string -> int β€” takes a link_mode, then string, then string list, then string, and returns an int. That's a whole little pipeline, and the signature ate.

mwah πŸ’‹ bestie, that's the whole Ccomp(3) page β€” served fresh by OCamldoc on 2026-06-22. πŸ’–

πŸ“¦ where this page comes from