Provided by: jbuilder_1.0~beta14-1_amd64 bug


       jbuilder-exec - Execute a command in a similar environment as if installation was


       jbuilder exec [OPTION]... PROG [ARGS]...


       jbuilder exec -- COMMAND should behave in the same way as if you do:

         $ jbuilder install
         $ COMMAND

       In particular if you run jbuilder exec ocaml, you will have access to the libraries
       defined in the workspace using your usual directives (#require for instance)


       --context=CONTEXT (absent=default)
           Run the command in this build context.

       --help[=FMT] (default=auto)
           Show this help in format FMT. The value FMT must be one of `auto', `pager', `groff' or
           `plain'. With `auto', the format is `pager` or `plain' whenever the TERM env var is
           `dumb' or undefined.

           Show version information.


       These options are common to all commands.

           Always print exception backtraces.

           In case of error, print the dependency path from the targets on the command line to
           the rule that failed.

           Debug the findlib sub-system.

           Use stricter compilation flags by default.

       -j JOBS (absent=4)
           Run no more than JOBS commands simultaneously.

           Do not buffer the output of commands executed by jbuilder. By default jbuilder buffers
           the output of subcommands, in order to prevent interleaving when multiple commands are
           executed in parallel. However, this can be an issue when debugging long running tests.
           With --no-buffer, commands have direct access to the terminal. Note that as a result
           their output won't be captured in the log file. You should use this option in
           conjunction with -j 1, to avoid interleaving. Additionally you should use --verbose as
           well, to make sure that commands are printed before they are being executed.

           Ignore stanzas referring to a package that is not in PACKAGES. PACKAGES is a
           comma-separated list of package names. Note that this has the same effect as deleting
           the relevant stanzas from jbuild files. It is mostly meant for releases. During
           development, it is likely that what you want instead is to build a particular
           <package>.install target.

       -p PACKAGES, --for-release-of-packages=PACKAGES
           Shorthand for --root . --only-packages PACKAGE. You must use this option in your
           <package>.opam files, in order to build only what's necessary when your project
           contains multiple packages as well as getting reproducible builds.

           Use this directory as workspace root instead of guessing it. Note that this option
           doesn't change the interpretation of targets given on the command line. It is only
           intended for scripts.

           Print detailed information about commands being run

           Use this specific workspace file instead of looking it up.


       Use `jbuilder COMMAND --help' for help on a single command.


       Check bug reports at