INSTALL.md

   1 CVC4 prerelease version 1.9
   2 ===========================
   3
   4 ## Building CVC4
   5
   6     ./contrib/get-antlr-3.4  # download and build ANTLR
   7     ./configure.sh   # use --prefix to specify a prefix (default: /usr/local)
   8                      # use --name=<PATH> for custom build directory
   9     cd <build_dir>   # default is ./build
  10     make             # use -jN for parallel build with N threads
  11     make check       # to run default set of tests
  12     make install     # to install into the prefix specified above
  13
  14 All binaries are built into `<build_dir>/bin`, the CVC4 library is built into
  15 `<build_dir>/lib`.
  16
  17 ## Supported Operating Systems
  18
  19 CVC4 can be built on Linux and macOS.  For Windows, CVC4 can be cross-compiled
  20 using Mingw-w64.  We recommend a 64-bit operating system.
  21
  22 On macOS, we recommend using Homebrew (https://brew.sh/) to install the
  23 dependencies.  We also have a Homebrew Tap available at
  24 https://github.com/CVC4/homebrew-cvc4 .
  25 To build a static binary for macOS, use:
  26 `./configure.sh --static --no-static-binary`.
  27
  28 ### Cross-compiling for Windows
  29
  30 Cross-compiling CVC4 with Mingw-w64 can be done as follows:
  31
  32 ```
  33   ./configure.sh --win64 --static <configure options...>
  34
  35   cd <build_dir>   # default is ./build
  36   make             # use -jN for parallel build with N threads
  37 ```
  38
  39 The built binary `cvc4.exe` is located in `<build_dir>/bin` and the CVC4 library
  40 can be found in `<build_dir>/lib`.
  41
  42 ## Build dependencies
  43
  44 The following tools and libraries are required to build and run CVC4.
  45 Versions given are minimum versions; more recent versions should be
  46 compatible.
  47
  48 - [GNU C and C++ (gcc and g++)](https://gcc.gnu.org)
  49   or [Clang](https://clang.llvm.org) (reasonably recent versions)
  50 - [CMake >= 3.9](https://cmake.org)
  51 - [GNU Bash](https://www.gnu.org/software/bash/)
  52 - [Python 3.x](https://www.python.org)
  53   + module [toml](https://pypi.org/project/toml/)
  54 - [GMP v4.2 (GNU Multi-Precision arithmetic library)](https://gmplib.org)
  55 - [libantlr3c v3.2 or v3.4 (ANTLR parser generator C support library)](http://www.antlr3.org/)
  56 - [Java >= 1.6](https://www.java.com)
  57
  58 Some features, such as the theory of floating-point numbers, require
  59 [optional dependencies](optional-dependencies) (see below).
  60
  61 ### Installing libantlr3c: ANTLR parser generator C support library
  62
  63 For libantlr3c, you can use the script `contrib/get-antlr-3.4`.
  64 This will download, patch, and install libantlr3c.
  65
  66 If you're on a 32-bit machine, or if you have difficulty building
  67 libantlr3c (or difficulty getting CVC4 to link against it), you
  68 may need to remove the configure option `--enable-64bit` in the script.
  69
  70 ### Warning: GCC 4.5.1
  71
  72 GCC version 4.5.1 seems to have a bug in the optimizer that may result in
  73 incorrect behavior (and wrong results) in many builds. This is a known problem
  74 for MiniSat, and since MiniSat is at the core of CVC4, a problem for CVC4.
  75 We recommend using a GCC version > 4.5.1.
  76
  77 ### Warning: Installing GMP via `contrib/get-gmp-dev`
  78
  79 Do **not** install GMP via the provided script `contrib/get-gmp-dev` unless
  80 your distribution
  81 * does not ship with the GMP configuration you need, e.g.,
  82   `contrib/get-gmp-dev` is used in `configure.sh` when cross-compiling GMP for
  83   Windows.
  84 * does not ship with static GMP libraries (e.g., Arch Linux)
  85   and you want to build CVC4 statically.
  86
  87 In most of the cases the GMP version installed on your system is the one you
  88 want and should use.
  89
  90 ## Optional Dependencies
  91
  92 ### SymFPU (Support for the Theory of Floating Point Numbers)
  93
  94 [SymFPU](https://github.com/martin-cs/symfpu/tree/CVC4)
  95 is an implementation of SMT-LIB/IEEE-754 floating-point operations in terms
  96 of bit-vector operations.
  97 It is required for supporting the theory of floating-point numbers and
  98 can be installed using the `contrib/get-symfpu` script.
  99 Configure CVC4 with `configure.sh --symfpu` to build with this dependency.
 100
 101 ### CaDiCaL (Optional SAT solver)
 102
 103 [CaDiCaL](https://github.com/arminbiere/cadical)
 104 is a SAT solver that can be used for solving non-incremental bit-vector
 105 problems with eager bit-blasting. This dependency may improve performance.
 106 It can be installed using the `contrib/get-cadical script`.
 107 Configure CVC4 with `configure.sh --cadical` to build with this dependency.
 108
 109 ### CryptoMiniSat (Optional SAT solver)
 110
 111 [CryptoMinisat](https://github.com/msoos/cryptominisat)
 112 is a SAT solver that can be used for solving bit-vector problems with eager
 113 bit-blasting. This dependency may improve performance.
 114 It can be installed using the `contrib/get-cryptominisat` script.
 115 Configure CVC4 with `configure.sh --cryptominisat` to build with this
 116 dependency.
 117
 118 ### Kissat (Optional SAT solver)
 119
 120 [Kissat](https://github.com/arminbiere/kissat)
 121 is a SAT solver that can be used for solving bit-vector problems with eager
 122 bit-blasting. This dependency may improve performance.
 123 It can be installed using the `contrib/get-kissat` script.
 124 Configure CVC4 with `configure.sh --kissat` to build with this
 125 dependency.
 126
 127 ### LFSC (The LFSC Proof Checker)
 128
 129 [LFSC](https://github.com/CVC4/LFSC) is required to check proofs internally
 130 with --check-proofs. It can be installed using the `contrib/get-lfsc` script.
 131 Configure CVC4 with `configure.sh --lfsc` to build with this dependency.
 132
 133 ### LibPoly (Optional polynomial library)
 134
 135 [LibPoly](https://github.com/SRI-CSL/libpoly) is required for CAD-based nonlinear reasoning.
 136 It can be installed using the `contrib/get-poly` script.
 137 Configure CVC4 with `configure.sh --poly` to build with this dependency.
 138
 139 ### CLN >= v1.3 (Class Library for Numbers)
 140
 141 [CLN](http://www.ginac.de/CLN)
 142 is an alternative multiprecision arithmetic package that may offer better
 143 performance and memory footprint than GMP.
 144 Configure CVC4 with `configure.sh --cln` to build with this dependency.
 145
 146 Note that CLN is covered by the [GNU General Public License, version 3](https://www.gnu.org/licenses/gpl-3.0.en.html).
 147 If you choose to use CVC4 with CLN support, you are licensing CVC4 under that
 148 same license.
 149 (Usually CVC4's license is more permissive than GPL, see the file `COPYING` in
 150 the CVC4 source distribution for details.)
 151
 152 ### glpk-cut-log (A fork of the GNU Linear Programming Kit)
 153
 154 [glpk-cut-log](https://github.com/timothy-king/glpk-cut-log/) is a fork of
 155 [GLPK](http://www.gnu.org/software/glpk/) (the GNU Linear Programming Kit).
 156 This can be used to speed up certain classes of problems for the arithmetic
 157 implementation in CVC4. (This is not recommended for most users.)
 158
 159 glpk-cut-log can be installed using the `contrib/get-glpk-cut-log` script.
 160 Note that the only installation option is manual installation via this script.
 161 CVC4 is no longer compatible with the main GLPK library.
 162 Configure CVC4 with `configure.sh --glpk` to build with this dependency.
 163
 164 Note that GLPK and glpk-cut-log are covered by the [GNU General Public License, version 3](https://www.gnu.org/licenses/gpl-3.0.en.html).
 165 If you choose to use CVC4 with GLPK support, you are licensing CVC4 under that
 166 same license.
 167 (Usually CVC4's license is more permissive; see above discussion.)
 168
 169 ### ABC library (Improved Bit-Vector Support)
 170
 171 [ABC](http://www.eecs.berkeley.edu/~alanmi/abc/) (A System for Sequential
 172 Synthesis and Verification) is a library for synthesis and verification of
 173 logic circuits. This dependency may improve performance of the eager
 174 bit-vector solver. When enabled, the bit-blasted formula is encoded into
 175 and-inverter-graphs (AIG) and ABC is used to simplify these AIGs.
 176
 177 ABC can be installed using the `contrib/get-abc` script.
 178 Configure CVC4 with `configure.sh --abc` to build with this dependency.
 179
 180 ### Editline library (Improved Interactive Experience)
 181
 182 The [Editline Library](https://thrysoee.dk/editline/) library is optionally
 183 used to provide command editing, tab completion, and history functionality at
 184 the CVC4 prompt (when running in interactive mode).  Check your distribution
 185 for a package named "libedit-dev" or "libedit-devel" or similar.
 186
 187 ### Boost C++ base libraries (Examples)
 188
 189 The [Boost](http://www.boost.org) C++ base library is needed for some examples
 190 provided with CVC4.
 191
 192 ### Google Test Unit Testing Framework (Unit Tests)
 193
 194 [Google Test](https://github.com/google/googletest) is required to optionally
 195 run CVC4's unit tests (included with the distribution).
 196 See [Testing CVC4](#Testing-CVC4) below for more details.
 197
 198 ## Language bindings
 199
 200 CVC4 provides a complete and flexible C++ API (see `examples/api` for
 201 examples). It further provides Java (see `examples/SimpleVC.java` and
 202 `examples/api/java`) and Python (see `examples/api/python`) API bindings.
 203
 204 Configure CVC4 with `configure.sh --<lang>-bindings` to build with language
 205 bindings for `<lang>`.
 206
 207 If you're interested in helping to develop, maintain, and test a language
 208 binding, please contact one of the project leaders.
 209
 210 ## Building the Examples
 211
 212 See `examples/README.md` for instructions on how to build and run the examples.
 213
 214 ## Testing CVC4
 215
 216 We use `ctest` as test infrastructure, for all command-line options of ctest,
 217 see `ctest -h`. Some useful options are:
 218
 219     ctest -R <regex>           # run all tests with names matching <regex>
 220     ctest -E <regex>           # exclude tests with names matching <regex>
 221     ctest -L <regex>           # run all tests with labels matching <regex>
 222     ctest -LE <regex>          # exclude tests with labels matching <regex>
 223     ctest                      # run all tests
 224     ctest -jN                  # run all tests in parallel with N threads
 225     ctest --output-on-failure  # run all tests and print output of failed tests
 226
 227 We have 4 categories of tests:
 228 - **examples** in directory `examples`
 229   (label: **example**)
 230 - **regression tests** (5 levels) in directory `test/regress`
 231   (label: **regressN** with N the regression level)
 232 - **api tests** in directory `test/api`
 233   (label: **api**)
 234 - **unit tests** in directory `test/unit`
 235   (label: **unit**)
 236
 237 ### Testing System Tests
 238
 239 The system tests are not built by default.
 240
 241     make apitests                         # build and run all system tests
 242     make <api_test>                       # build test/system/<system_test>.<ext>
 243     ctest api/<api_test>                  # run test/system/<system_test>.<ext>
 244
 245 All system test binaries are built into `<build_dir>/bin/test/system`.
 246
 247 We use prefix `api/` + `<api_test>` (for `<api_test>` in `test/api`)
 248 as test target name.
 249
 250     make ouroborous                       # build test/api/ouroborous.cpp
 251     ctest -R ouroborous                   # run all tests that match '*ouroborous*'
 252                                           # > runs api/ouroborous
 253     ctest -R ouroborous$                  # run all tests that match '*ouroborous'
 254                                           # > runs api/ouroborous
 255     ctest -R api/ouroborous$              # run all tests that match '*api/ouroborous'
 256                                           # > runs api/ouroborous
 257 ### Testing Unit Tests
 258
 259 The unit tests are not built by default.
 260
 261 Note that CVC4 can only be configured with unit tests in non-static builds with
 262 assertions enabled.
 263
 264     make units                            # build and run all unit tests
 265     make <unit_test>                      # build test/unit/<subdir>/<unit_test>.<ext>
 266     ctest unit/<subdir>/<unit_test>       # run test/unit/<subdir>/<unit_test>.<ext>
 267
 268 All unit test binaries are built into `<build_dir>/bin/test/unit`.
 269
 270 We use prefix `unit/` + `<subdir>/` + `<unit_test>` (for `<unit_test>` in
 271 `test/unit/<subdir>`) as test target name.
 272
 273     make map_util_black                   # build test/unit/base/map_util_black.cpp
 274     ctest -R map_util_black               # run all tests that match '*map_util_black*'
 275                                           # > runs unit/base/map_util_black
 276     ctest -R base/map_util_black$         # run all tests that match '*base/map_util_black'
 277                                           # > runs unit/base/map_util_black
 278     ctest -R unit/base/map_util_black$    # run all tests that match '*unit/base/map_util_black'
 279                                           # > runs unit/base/map_util_black
 280
 281 ### Testing Regression Tests
 282
 283 We use prefix `regressN/` + `<subdir>/` + `<regress_test>` (for `<regress_test>`
 284 in level `N` in `test/regress/regressN/<subdir>`) as test target name.
 285
 286     ctest -L regress                      # run all regression tests
 287     ctest -L regress0                     # run all regression tests in level 0
 288     ctest -L regress[0-1]                 # run all regression tests in level 0 and 1
 289     ctest -R regress                      # run all regression tests
 290     ctest -R regress0                     # run all regression tests in level 0
 291     ctest -R regress[0-1]                 # run all regression tests in level 0 and 1
 292     ctest -R regress0/bug288b             # run all tests that match '*regress0/bug288b*'
 293                                           # > runs regress0/bug288b
 294 ### Custom Targets
 295
 296 All custom test targets build and run a preconfigured set of tests.
 297
 298 - `make check [-jN] [ARGS=-jN]`
 299   The default build-and-test target for CVC4, builds and runs all examples,
 300   all system and unit tests, and regression tests from levels 0 to 2.
 301
 302 - `make systemtests [-jN] [ARGS=-jN]`
 303   Build and run all system tests.
 304
 305 - `make units [-jN] [ARGS=-jN]`
 306   Build and run all unit tests.
 307
 308 - `make regress [-jN] [ARGS=-jN]`
 309   Build and run regression tests from levels 0 to 2.
 310
 311 - `make runexamples [-jN] [ARGS=-jN]`
 312   Build and run all examples.
 313
 314 - `make coverage [-jN] [ARGS=-jN]`
 315   Build and run all tests (system and unit tests, regression tests level 0-4)
 316   with gcov to determine code coverage.
 317
 318 We use `ctest` as test infrastructure, and by default all test targets
 319 are configured to **run** in parallel with the maximum number of threads
 320 available on the system. Override with `ARGS=-jN`.
 321
 322 Use `-jN` for parallel **building** with `N` threads.
 323
 324
 325 ## Recompiling a specific CVC4 version with different LGPL library versions
 326
 327 To recompile a specific static binary of CVC4 with different versions of the
 328 linked LGPL libraries perform the following steps:
 329
 330 1. Make sure that you have installed the desired LGPL library versions.
 331    You can check the versions found by CVC4's build system during the configure
 332    phase.
 333
 334 2. Determine the commit sha and configuration of the CVC4 binary
 335 ```
 336 cvc4 --show-config
 337 ```
 338 3. Download the specific source code version:
 339 ```
 340 wget https://github.com/CVC4/CVC4/archive/<commit-sha>.tar.gz
 341 ```
 342 4. Extract the source code
 343 ```
 344 tar xf <commit-sha>.tar.gz
 345 ```
 346 5. Change into source code directory
 347 ```
 348 cd CVC4-<commit-sha>
 349 ```
 350 6. Configure CVC4 with options listed by `cvc4 --show-config`
 351 ```
 352 ./configure.sh --static <options>
 353 ```
 354
 355 7. Follow remaining steps from [build instructions](#building-cvc4)