Documentation for JavaScript targets

This commit is contained in:
hhugo 2017-05-04 14:11:42 +01:00 committed by GitHub
parent bfb01f4bc3
commit 031d57a70a
1 changed files with 4 additions and 3 deletions

View File

@ -409,9 +409,10 @@ format of executable stanzas is as follows:
=<name>= is a module name that contains the main entry point of the =<name>= is a module name that contains the main entry point of the
executable. There can be additional modules in the current directory, executable. There can be additional modules in the current directory,
you only need to specify the entry point. Given an =executable= stanza you only need to specify the entry point. Given an =executable= stanza
with =(name <name>)=, Jbuilder will know how to build =<name>.exe= and with =(name <name>)=, Jbuilder will know how to build =<name>.exe=,
=<name>.bc=. =<name>.exe= is a native code executable and =<name>.bc= =<name>.bc= and =<name>.bc.js=. =<name>.exe= is a native code executable, =<name>.bc=
is a bytecode executable which requires =ocamlrun= to run. is a bytecode executable which requires =ocamlrun= to run and =<name>.bc.js=
is a JavaScript generated using js_of_ocaml.
Note that in case native compilation is not available, =<name>.exe= 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 will in fact be a custom byte-code executable. Custom in the sense of