1WHY3CONFIG(1) User Commands WHY3CONFIG(1)
2
3
4
6 why3config - detect provers usable by why3
7
9 why3config [OPTIONS]
10
12 Why3 must be configured to access external provers. Typically, this is
13 done by either running this tool or using the menu File/Detect provers
14 of the IDE. This must be redone each time a new prover is installed.
15
16 The provers Why3 attempts to detect are described in the human-readable
17 file /usr/share/why3/provers-detection-data.conf. Advanced users may
18 try to modify this file to add support for detection of other provers.
19
20 The result of provers detection is stored in the user's configuration
21 file (~/.why3.conf). This file is also human-readable, and advanced
22 users may modify it to experiment with different ways of calling
23 provers, e.g., different versions of the same prover, or with different
24 options.
25
26 If the user's configuration file is already present, why3config will
27 only reset unset variables to default values, but will not try to
28 detect provers. The option -detect-provers should be used to force
29 Why3 to detect again the available provers and to replace them in the
30 configuration file. The option -detect-plugins will do the same for
31 plugins.
32
34 -C, --config <file>
35 The configuration file to create.
36
37 --detect-provers
38 Search for provers in $PATH.
39
40 --detect-plugins
41 Search for plugins in the default library directory.
42
43 --detect
44 Search for both provers and plugins.
45
46 --install-plugin
47 Install a plugin to the actual library directory.
48
49 --dont-save
50 Do not modify the configuration file.
51
52 --list-debug-flags
53 List known debug flags.
54
55 --debug-all
56 Set all debug flags except parse_only and type_only.
57
58 --debug <flag>
59 Set a debug flag.
60
61 --version
62 Print version information.
63
64 -help, --help
65 Show a list of options.
66
68 why(1), why3-cpulimit(1), why3bench(1), why3doc(1), why3ide(1),
69 why3ml(1), why3realize(1), why3replayer(1)
70
71
72
73why3 1.3.1 WHY3CONFIG(1)