The jenga monad. It has two pieces to it:
Dep.path and all the functions that return a unit t add to. The final value of this accumulator is the dependencies of the action in Rule.create and Dep.action, and what gets built in the case of Rule.aliasTo make clear the distinction between the two, take:
val path : Path.t -> unit t val contents : Path.t -> string t
path simply says that the surrounding Rule.create (for instance) will read the contents of that file. contents allows to create different action depending on the contents of the file.
It's highly recommended to use parallel combinators like both and all in preference to bind. Using bind is inherently sequential, whereas usually work in a build system can be done in parallel.
val sexp_of_t :
('a -> Ppx_sexp_conv_lib.Sexp.t) ->
'a t ->
Ppx_sexp_conv_lib.Sexp.tval return : 'a -> 'a tval deferred : (unit -> 'a Async.Deferred.t) -> 'a tlet v = memoize ~name t behaves like t, except with caching: using v in several computations will not result in duplicate evaluations of t. name is used in displayed in errors, or in the case of dependency cycles.
getenv v provides access to a registered environment variable, responding to changes notified to jenga via the setenv RPC/command-line.
group_dependencies t is equivalent to t, however jenga will be careful to avoid duplicating the set of dependencies that have been declared. This is best used under an alias, as the alias will allow to share the computation as well.
source_if_it_exists Dont treat path as a goal (i.e. don't force it to be built) Just depend on its contents, if it exists. It's ok if it doesn't exist.
The semantics of glob_listing and glob_change includes files which exist on the file-system AND files which are buildable by some jenga rule. Therefore it is an error (dependency cycle) to glob a directory while generating the scheme for that same directory. Use Scheme.glob instead.
Versions with old semantics: only includes files on the file-system.
file_exists makes the information about file existence available to the rules, but does not declare it as an action dependency.
file_exists makes the information about file existence available to the rules, but does not declare it as an action dependency.
file_existence declares an action dependency on file existence
module List : sig ... end