Installation

$ opam install mcrunch

Usage

The simplest invocation takes a file and writes an OCaml module to stdout:

$ mcrunch -f foo.txt
let foo_txt = [| "\x66\x6f\x6f\x0a" |]

The OCaml binding name is derived from the filename, with characters like . and % replaced by underscores. You can also specify the binding name explicitly using the name:filename syntax:

$ mcrunch -f contents:foo.txt
let contents = [| "\x66\x6f\x6f\x0a" |]

Multiple files can be crunched into a single module:

$ mcrunch -f foo.txt -f bar.txt -o assets.ml

If a filename contains the character :, use the prefix -: to let mcrunch infer the name automatically:

$ mcrunch -f -:path:to:file

Options

• -f, --file [NAME|-:]FILENAME specifies a file to crunch. This option can be repeated to include multiple files. An optional name can be given before the filename, separated by :.
• -d, --directory DIRECTORY specifies a directory to crunch. It is walked recursively and every regular file found is crunched as if it had been given with --file, the path walked to it — DIRECTORY included — being used to infer the OCaml name. Entries are visited in a stable order, so the output only depends on the contents of the directory. This option can be repeated.
• -e, --ext EXTENSION restricts --directory to the files carrying this extension. The leading . is optional. This option can be repeated. Without it, every file is crunched.
• --lookup=NAME also emits a function mapping each crunched filename to its contents, so that they can be reached by name at run-time rather than through the bindings mcrunch infers. The function NAME returns an option. In this mode, it is possible to associate a file with its name even if the latter cannot be ocamlify (as an OCaml identifier).
• -o, --output FILENAME writes the output to the given file instead of stdout. The file must not already exist. Use - for stdout (the default).
• -a, --array serializes each file's contents as an array of strings. This is the default.
• -l, --list serializes each file's contents as a list of strings instead of an array.
• -s, --string serializes each file's contents as a single string instead of an array of strings.
• -c, --cols COLS sets the number of octets per line in the hex output. Default is 16, maximum is 256.
• -u uses uppercase hex letters instead of the default lowercase.
• --with-comments appends a human-readable ASCII representation of each line as an OCaml comment:

$ mcrunch -f foo.txt --with-comments
let foo_txt = [| "\x66\x6f\x6f\x0a" |]                                                 (* foo.             *)

Note that comments are not supported for --string output. A warning is printed on stderr:

$ mcrunch --string --with-comments -f foo.txt
Comments are not supported for string output. Not outputting comments.
let foo_txt = "\x66\x6f\x6f\x0a"

Example

Given two files index.html and style.css, you can generate an OCaml module that embeds both:

$ mcrunch -f index.html -f style.css -o static.ml

The resulting static.ml contains two bindings, index_html and style_css, each holding the full file contents as a string array. You can then reference these values from your OCaml program and reconstruct the original content with String.concat "" (for arrays, Array.to_list first).

A whole tree of assets can be embedded at once, optionally restricted to some extensions:

$ mcrunch -d static -e html -e css -o static.ml
let static_index_html = [| … |]
let static_style_css = [| … |]

When the file to serve is only known at run-time, --lookup gives the module a function to reach it by path, and lets mcrunch name the bindings so that any filename can be crunched:

$ mcrunch -d static -s --lookup -o static.ml
let d_0 = "…"
let d_1 = "…"

let read = function
  | "static/index.html" -> Some d_0
  | "static/style.css" -> Some d_1
  | _ -> None

With --string, read hands back the string literal itself: nothing is concatenated or copied, and the contents stay where the linker put them.