matthieu
/
dune
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Clarify availability of native compilation

This commit is contained in:
Jeremie Dimino 2017-05-29 13:18:55 +01:00
parent c73b1f1fe3
commit df3ac59d72
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/jbuild.rst
View File

@ -200,9 +200,12 @@ JavaScript generated using js_of_ocaml.
Note that in case native compilation is not available, ``<name>.exe``
will in fact be a custom byte-code executable. Custom in the sense of
``ocamlc -custom``, meaning that it is a native executable that
embeds the ``ocamlrun`` virtual machine as well as the byte code. As
such you can always rely on ``<name>.exe`` being available.
``ocamlc -custom``, meaning that it is a native executable that embeds
the ``ocamlrun`` virtual machine as well as the byte code. As such you
can always rely on ``<name>.exe`` being available.
Native compilation is considered not available when there is no
``ocamlopt`` binary at the same place as where ``ocamlc`` was found.
``<optional-fields>`` are: