1
- # WHAT ARCHITECTURE?
1
+ #WHAT ARCHITECTURE ?
2
2
3
3
CPROVER now needs a C++11 compliant compiler and is known to work in the
4
4
following environments:
@@ -18,7 +18,7 @@ past, but are not actively tested:
18
18
- Solaris 11
19
19
- FreeBSD 11
20
20
21
- # Building using CMake
21
+ #Building using CMake
22
22
23
23
Building with CMake is supported across Linux, MacOS X and Windows with Visual
24
24
Studio 2019. There are also hand-written make files which can be used to build
@@ -118,7 +118,7 @@ files.
118
118
complete set of built binaries can be found in `./build/bin` once the build
119
119
is complete.
120
120
121
- # Building using hand- written make files.
121
+ #Building using hand - written make files.
122
122
123
123
The rest of this section is split up based on the platform being built on.
124
124
Please read the section appropriate for your machine.
@@ -253,7 +253,7 @@ Maven 3 manually.
253
253
gmake -C jbmc/src
254
254
```
255
255
256
- # WORKING WITH ECLIPSE
256
+ #WORKING WITH ECLIPSE
257
257
258
258
To work with Eclipse, do the following:
259
259
@@ -270,7 +270,7 @@ the need to integrate JBMC as a separate project. Be aware that you need to
270
270
change the build location (Select project in Eclipse -> Properties -> C/C++
271
271
Build) to one of the src directories.
272
272
273
- # WORKING WITH DOCKER
273
+ #WORKING WITH DOCKER
274
274
275
275
To compile and run the tools in a Docker container, do the following:
276
276
@@ -284,9 +284,9 @@ To compile and run the tools in a Docker container, do the following:
284
284
that contains the tests to the container. A possible invocation that does that
285
285
is: `$ docker run --mount type=bind,source=local/path/with/files,target=/mnt/analysis -i t cbmc`. In the
286
286
resulting container, the files present in the local file system under
287
- `local/path/with/files` will be present under `/mnt/analysis`.
287
+ `local/path/with/files` will be present under `/mnt/analysis`.
288
288
289
- # OPTIONS AND VARIABLES
289
+ #OPTIONS AND VARIABLES
290
290
291
291
## Compiling with CUDD
292
292
@@ -482,3 +482,48 @@ successfully on Windows or macOS.
482
482
The argument for the IPASIR parameter gives the build system the location for
483
483
the IPASIR headers, which is needed for the cbmc includes of ` ipasir.h ` . The
484
484
compiled binary will be placed in ` cbmc/src/cbmc/cbmc ` .
485
+ This document assumes you have already been able to build CPROVER on
486
+ your chosen architecture.
487
+
488
+ #RUNNING REGRESSION AND UNIT TESTS
489
+
490
+ Regression and unit tests can be run using cmake or make. Your choice here
491
+ should be the same as the compiling of the project itself.
492
+
493
+ Note that running all regression and unit tests can be slow when a debug
494
+ build of CPROVER is used.
495
+
496
+ ## CMAKE
497
+
498
+ This can be done by changing to the directory you built the
499
+ project in with cmake and running ctest as follows.
500
+ ```
501
+ cd <build_dir>
502
+ ctest . -V -L CORE
503
+ ```
504
+ You can also specify a pattern of tests to run as follows.
505
+ ```
506
+ ctest . -V -L CORE -R <pattern>
507
+ ```
508
+ For example
509
+ ```
510
+ ctest . -V -L CORE -R goto
511
+ ```
512
+ that will run all CORE tests that include ` goto ` in their
513
+ name.
514
+
515
+ ## MAKE
516
+
517
+ The regression and unit tests are handled differently in the
518
+ make system. To run the regressions tests change to the
519
+ ` regression ` directory and simply running make as follows.
520
+ ```
521
+ cd regression
522
+ make test
523
+ ```
524
+ To run the unit tests, change into the ` unit ` directory and
525
+ then run make as follows.
526
+ ```
527
+ cd unit
528
+ make test
529
+ ```
0 commit comments