OCaml toolchain configuration.
Thid module provides access to the OCaml toolchain configuration as output by ocaml{c,opt} -config.
It also provides bits to orchestrate byte and native OCaml builds.
val find : string -> t -> string optionfind f c looks up the field f in configuration c. See ocamlc -config for the list of fields.
val version : t -> int * int * int * string optionversion c is the compiler version string "major.minor[.patchlevel][+additional-info]" parsed using (major, minor, patch, additional-info). If patch-level is absent it is turned into a 0.
val where : t -> B00_std.Fpath.twhere c is the location of OCaml's library directory.
val asm_ext : t -> B00_std.Fpath.extasm_ext is the file extension for assembly files.
val dll_ext : t -> B00_std.Fpath.extdll_ext is the file extension for C dynamic libraries.
val exe_ext : t -> B00_std.Fpath.extext_ext is the file extension for executable binaries.
val lib_ext : t -> B00_std.Fpath.extext_lib is the file extension for C static libraries.
val obj_ext : t -> B00_std.Fpath.extobj_ext is the file extension for C object files.
val to_string_map : t -> string B00_std.String.Map.tto_string_map c are the fields of c as a string map.
val of_string_map : string B00_std.String.Map.t -> (t, string) resultof_string_map m is a configuration from string map m. m needs at least a "version" key otherwise the function errors.
val write : B00.Memo.t -> comp:B00.Tool.t -> o:B00_std.Fpath.t -> unitwrite m ~o writes the toolchain configuration to o by running comp with -config.
val read : B00.Memo.t -> B00_std.Fpath.t -> t B00.Memo.fiberread m file reads a toolchain configuration from file.
val of_string : ?file:B00_std.Fpath.t -> string -> (t, string) resultof_string ~file data parses toolchain configuration from data as output by the compiler's -config option assuming it was read from file file (defaults to B00_std.Os.File.dash.
XXX Maybe move that to B0_ocaml.
In a build it is desirable to know which code is being produced because if both are produced the compilers may compete to produce some of the shared build artefacts. The following store keys allow to express build code desires and determine the actual decision.
val build_code : [ built_code | `Auto ] B00.Store.keybuild_code indicates which code should be built, default determines to `Auto. `Auto indicates `Native should be used if ocamlopt can be found in the memo environment and `Byte otherwise.
val built_code : built_code B00.Store.keybuild_code is a memo key indicating the built code. By default determines by consulting build_code.
val key : t B00.Store.keykey is a memo key store with the OCaml configuration.
val exists : B00.Memo.t -> bool B00.Memo.fiberval if_exists :
B00.Memo.t ->
(unit -> 'a B00.Memo.fiber) ->
'a option B00.Memo.fiberval stdlib_dir : B00.Memo.t -> unit -> B00_std.Fpath.t B00.Memo.fiber