.\" Pipe this output to groff -Tutf8 | less
.\"
.mso an.tmac
.TH "jbuilder-rules" 1 "" "Jbuilder 1.0+beta20" "Jbuilder Manual"
.\" Disable hyphenation and ragged-right
.nh
.ad l
.SH NAME
.P
jbuilder\N'45'rules \N'45' Dump internal rules\N'46'
.SH SYNOPSIS
.P
\fBjbuilder rules\fR [\fIOPTION\fR]\N'46'\N'46'\N'46' [\fITARGET\fR]\N'46'\N'46'\N'46'
.SH DESCRIPTION
.P
Dump Jbuilder internal rules for the given targets\N'46' If no targets are given, dump all the internal rules\N'46'
.P
By default the output is a list of S\N'45'expressions, one S\N'45'expression per rule\N'46' Each S\N'45'expression is of the form:
.P
.nf
  ((deps    (<dependencies>))
   (targets (<targets>))
   (context <context\N'45'name>)
   (action  <action>))
.fi
.P
\fB<context\N'45'name>\fR is the context is which the action is executed\N'46' It is omitted if the action is independant from the context\N'46'
.P
\fB<action>\fR is the action following the same syntax as user actions, as described in the manual\N'46'
.SH OPTIONS
.TP 4
\fB\N'45'f\fR, \fB\N'45'\N'45'force\fR
Force actions associated to aliases to be re\N'45'executed even if their dependencies haven\N'39't changed\N'46'
.TP 4
\fB\N'45'\N'45'help\fR[=\fIFMT\fR] (default=auto)
Show this help in format \fIFMT\fR\N'46' The value \fIFMT\fR must be one of `auto\N'39', `pager\N'39', `groff\N'39' or `plain\N'39'\N'46' With `auto\N'39', the format is `pager` or `plain\N'39' whenever the \fBTERM\fR env var is `dumb\N'39' or undefined\N'46'
.TP 4
\fB\N'45'm\fR, \fB\N'45'\N'45'makefile\fR
Output the rules in Makefile syntax\N'46'
.TP 4
\fB\N'45'o\fR \fIFILE\fR
Output to a file instead of stdout\N'46'
.TP 4
\fB\N'45'r\fR, \fB\N'45'\N'45'recursive\fR
Print all rules needed to build the transitive dependencies of the given targets\N'46'
.TP 4
\fB\N'45'\N'45'version\fR
Show version information\N'46'
.SH COMMON OPTIONS
.P
These options are common to all commands\N'46'
.TP 4
\fB\N'45'\N'45'auto\N'45'promote\fR
Automatically promote files\N'46' This is similar to running \fBjbuilder promote\fR after the build\N'46'
.TP 4
\fB\N'45'\N'45'config\N'45'file\fR=\fIFILE\fR
Load this configuration file instead of the default one\N'46'
.TP 4
\fB\N'45'\N'45'debug\N'45'backtraces\fR
Always print exception backtraces\N'46'
.TP 4
\fB\N'45'\N'45'debug\N'45'dependency\N'45'path\fR
In case of error, print the dependency path from the targets on the command line to the rule that failed\N'46' 
.TP 4
\fB\N'45'\N'45'debug\N'45'findlib\fR
Debug the findlib sub\N'45'system\N'46'
.TP 4
\fB\N'45'\N'45'dev\fR
Use stricter compilation flags by default\N'46'
.TP 4
\fB\N'45'\N'45'diff\N'45'command\fR=\fIVAL\fR
Shell command to use to diff files
.TP 4
\fB\N'45'\N'45'display\fR=\fIMODE\fR
Control the display mode of Jbuilder\N'46' See \fBdune\N'45'config(5)\fR for more details\N'46'
.TP 4
\fB\N'45'\N'45'ignore\N'45'promoted\N'45'rules\fR
Ignore rules with (mode promote)
.TP 4
\fB\N'45'j\fR \fIJOBS\fR
Run no more than \fIJOBS\fR commands simultaneously\N'46'
.TP 4
\fB\N'45'\N'45'no\N'45'buffer\fR
Do not buffer the output of commands executed by jbuilder\N'46' By default jbuilder buffers the output of subcommands, in order to prevent interleaving when multiple commands are executed in parallel\N'46' However, this can be an issue when debugging long running tests\N'46' With \fB\N'45'\N'45'no\N'45'buffer\fR, commands have direct access to the terminal\N'46' Note that as a result their output won\N'39't be captured in the log file\N'46' You should use this option in conjunction with \fB\N'45'j 1\fR, to avoid interleaving\N'46' Additionally you should use \fB\N'45'\N'45'verbose\fR as well, to make sure that commands are printed before they are being executed\N'46'
.TP 4
\fB\N'45'\N'45'no\N'45'config\fR
Do not load the configuration file
.TP 4
\fB\N'45'\N'45'only\N'45'packages\fR=\fIPACKAGES\fR
Ignore stanzas referring to a package that is not in \fBPACKAGES\fR\N'46' \fBPACKAGES\fR is a comma\N'45'separated list of package names\N'46' Note that this has the same effect as deleting the relevant stanzas from jbuild files\N'46' It is mostly meant for releases\N'46' During development, it is likely that what you want instead is to build a particular \fB<package>\N'46'install\fR target\N'46'
.TP 4
\fB\N'45'p\fR \fIPACKAGES\fR, \fB\N'45'\N'45'for\N'45'release\N'45'of\N'45'packages\fR=\fIPACKAGES\fR
Shorthand for \fB\N'45'\N'45'root \N'46' \N'45'\N'45'only\N'45'packages PACKAGE \N'45'\N'45'promote ignore \N'45'\N'45'no\N'45'config\fR\N'46' You must use this option in your \fI<package>\N'46'opam\fR files, in order to build only what\N'39's necessary when your project contains multiple packages as well as getting reproducible builds\N'46'
.TP 4
\fB\N'45'\N'45'root\fR=\fIDIR\fR
Use this directory as workspace root instead of guessing it\N'46' Note that this option doesn\N'39't change the interpretation of targets given on the command line\N'46' It is only intended for scripts\N'46'
.TP 4
\fB\N'45'\N'45'verbose\fR
Same as \fB\N'45'\N'45'display verbose\fR
.TP 4
\fB\N'45'\N'45'workspace\fR=\fIFILE\fR
Use this specific workspace file instead of looking it up\N'46'
.TP 4
\fB\N'45'x\fR \fIVAL\fR
Cross\N'45'compile using this toolchain\N'46'
.SH MORE HELP
.P
Use `\fBjbuilder\fR \fICOMMAND\fR \N'45'\N'45'help\N'39' for help on a single command\N'46'
.SH BUGS
.P
Check bug reports at https://github\N'46'com/ocaml/dune/issues