In short, installation proceeds as follows.
After unpacking the distribution, go to the newly created directory why3-0.87.3. Compilation must start with a configuration phase which is run as
This analyzes your current configuration and checks if requirements hold. Compilation requires:
ocaml ocaml-native-compilersIt is also installable from sources, downloadable from the site http://caml.inria.fr/ocaml/
For some of the Why3 tools, additional OCaml libraries are needed:
liblablgtk2-ocaml-dev liblablgtksourceview2-ocaml-devIt is also installable from sources, available from the site http://wwwfun.kurims.kyoto-u.ac.jp/soft/olabl/lablgtk.html
libsqlite3-ocaml-devIt is also installable from sources, available from the site http://ocaml.info/home/ocaml_sources.html#ocaml-sqlite3
If you want to use the specific Coq features, i.e. the Coq tactic (Section 9.3.1) and Coq realizations (Section 9.2), then Coq has to be installed before Why3. Look at the summary printed at the end of the configuration script to check if Coq has been detected properly. Similarly, for using PVS (Section 9.5) or Isabelle (Section 9.4) to discharge proofs, PVS and Isabelle must be installed before Why3. You should check that those proof assistants are correctly detected by the configure script.
When configuration is finished, you can compile Why3.
Installation is performed (as super-user if needed) using
Installation can be tested as follows:
why3 config --detect
$ cd examples $ why3 replay logic/scottish-private-club Opening session... done Progress: 4/4 1/1 Everything OK. $ why3 replay programs/same_fringe Opening session... done Progress: 12/12 3/3 Everything OK.
It is not mandatory to install Why3 into system directories. Why3 can be configured and compiled for local use as follows:
./configure --enable-local make
The Why3 executables are then available in the subdirectory bin/. This directory can be added in your PATH.
By default, the Why3 API is not installed. It can be installed using
Why3 can use a wide range of external theorem provers. These need to be installed separately, and then Why3 needs to be configured to use them. There is no need to install automatic provers, e.g. SMT solvers, before compiling and installing Why3.
For installation of external provers, please refer to the specific section about provers on the Web page http://why3.lri.fr/.
For configuring Why3 to use the provers, follow instructions given in Section 6.1.
Why3 is able to use several versions of the same
prover, e.g. it can use both CVC3 2.2 and CVC3 2.4.1 at the same time.
The automatic detection of provers looks for typical names for their
executable command, e.g. cvc3 for CVC3. However, if you
install several version of the same prover it is likely that you would
use specialized executable names, such as cvc3-2.2 or
cvc3-2.4.1. To allow the Why3 detection process to recognize
these, you can use the option
--add-prover with the
config command, e.g.
why3 config --detect --add-prover cvc3-2.4 /usr/local/bin/cvc3-2.4.1
the first argument (here
cvc3-2.4) must be one of the class of
provers known in the file
/usr/local/share/why3 after installation. See
Appendix 10.2 for details.
If you happen to upgrade a prover, e.g. installing CVC3 2.4.1 in place of CVC3 2.2, then the proof sessions formerly recorded will still refer to the old version of the prover. If you open one such a session with the GUI, and replay the proofs, you will be asked to choose between 3 options:
Notice that if the prover under consideration is an interactive one, then the copy option will duplicate also the edited proof scripts, whereas the upgrade-without-archive option will just reuse the former proof scripts.
Your choice between the three options above will be recorded, one for each prover, in the Why3 configuration file. Within the GUI, you can discard these choices via the Preferences dialog.
Outside the GUI, the prover upgrades are handled as follows. The replay command will just ignore proof attempts marked as archived. Conversely, a non-archived proof attempt with a non-existent prover will be reported as a replay failure. The session command performs move or copy operations on proof attempts in a fine-grained way, using filters, as detailed in Section 6.6.