Skip to content

Commit

Permalink
Update doc
Browse files Browse the repository at this point in the history
Signed-off-by: Nicolás Ojeda Bär <n.oje.bar@gmail.com>
  • Loading branch information
nojb committed Jul 22, 2019
1 parent 9c6b553 commit f14fb4c
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
6 changes: 3 additions & 3 deletions CHANGES.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,9 +17,6 @@

- Enable `(explicit_js_mode)` by default. (#1941, @nojb)

- Add (add-to-path) field in (context) definitions.
(#2426, @nojb)

1.11.0 (unreleased)
-------------------

Expand Down Expand Up @@ -117,6 +114,9 @@
targets, and a switch `(explicit_js_mode)` to require this mode in order to
declare JS targets corresponding to executables. (#1941, @nojb)

- Add (paths ...) field in (context) definitions.
(#2426, @nojb)

1.10.0 (04/06/2019)
-------------------

Expand Down
6 changes: 3 additions & 3 deletions doc/usage.rst
Original file line number Diff line number Diff line change
Expand Up @@ -500,9 +500,9 @@ context or can be the description of an opam switch, as follows:
- ``(host <host_context>)`` choose a different context to build binaries that
are meant to be executed on the host machine, such as preprocessors.

- ``(add-to-path <string list>)`` allows to extend the value of PATH for the
context. The resulting value will be used for resolution of binaries
(including the compiler tools).
- ``(paths (<var1> <val1>) .. (<varN> <valN>))`` allows to set the value of
PATH-like variables in this context. For each variable, the value is specified
using the :ref:`ordered-set-language`.

Both ``(default ...)`` and ``(opam ...)`` accept a ``targets`` field in order to
setup cross compilation. See :ref:`advanced-cross-compilation` for more
Expand Down

0 comments on commit f14fb4c

Please sign in to comment.