package b0

You can search for identifiers within the package.

in-package search v0.2.0

Software construction and deployment kit

Install

Dune Dependency

erratique.ch Readme Changelog ISC; BSD-2-Clause License Edit opam file Versions (6)

Authors

T

The b0 programmers

Maintainers

Daniel Bünzli

Sources

b0-0.0.2.tbz

sha512=78fd9e53b84cf5d6bf497adaf4b6d7d974134044318639cdfe5e01c7faaa8d987d04769abe3b3b1cbdb937132e21d8723dc185cd3c68433a793278907a8e757e

doc/b0_b00_kit/B00_odoc/Compile/index.html

Module `B00_odoc.Compile`

Compiling .cmi, .cmti, .cmt and .mld files to .odoc files.

Compile

module Dep : sig ... end

Compilation dependencies, for compiling .cmi, .cmti or .cmt files to .odoc files.

module Writes : sig ... end

Compilation writes, files written by compiling a .cmi, .cmti, .cmt or .mld file to an .odoc file.

val cmd : 
  ?resolve_forward_deps:bool ->
  ?hidden:bool ->
  B00.Memo.t ->
  odoc_deps:B00_std.Fpath.t list ->
  writes:B00_std.Fpath.t list ->
  pkg:string ->
  B00_std.Fpath.t ->
  o:B00_std.Fpath.t ->
  unit

cmd m ~resolve_forward_deps ~hidden ~odoc_deps ~writes ~pkg cobj o compiles the compilation object cobj part of package pkg to destination odoc file o.

odoc_deps are the odoc files the compilation of cobj reads. They can be obtained by resolving the result of Dep on cobj.
writes specifies the writes of the command they can be obtained via Writes.
resolve_forward_deps and hidden are the corresponding odoc options. See odoc compile --help.

Convenience

val to_odoc : 
  B00.Memo.t ->
  ?hidden:bool ->
  pkg:string ->
  odoc_deps:B00_std.Fpath.t list ->
  B00_std.Fpath.t ->
  o:B00_std.Fpath.t ->
  unit

to_odoc m ~hidden ~pkg ~odoc_deps obj ~o compiles obj (which can be any of a .cmi, .cmt, .cmti or .mld file) to an odoc file o assuming it depends on odoc_deps and is part of package pkg.

On This Page

Compile
Convenience