Skip to content

Commit 4bca13b

Browse files
author
owen-jones-diffblue
authored
Merge pull request #3384 from yumibagge/doc/cleanup-cprover-compilation-and-development
[DOC-127]doc/cleanup-cprover-compilation-and-development
2 parents 3469b19 + 01dd28c commit 4bca13b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/architectural/compilation-and-development.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ FreeBSD 11, MacOS X and Windows.
2222

2323
There is also support for compiling using CMake. Instructions are
2424
available in
25-
[COMPILING.md](https://github.com/diffblue/cbmc/blob/develop/COMPILING.md#working-with-cmake-experimental)
25+
[COMPILING.md](https://github.com/diffblue/cbmc/blob/develop/COMPILING.md#working-with-cmake)
2626
in the root of the CBMC repository.
2727

2828

@@ -93,7 +93,7 @@ folders.
9393
If you have compiled using CMake then you can run the regression tests (and
9494
the unit tests) using CTest.
9595

96-
Here are two example commands, to be run from the build directory:
96+
Here are two example commands, to be run from the `build/` directory:
9797

9898
ctest -V -L CORE -R cpp
9999
ctest -V -L CORE -R cpp -E cbmc-cpp
@@ -112,7 +112,7 @@ list which tests it will run without actually running them.
112112
\subsubsection compilation-and-development-subsubsection-running-regression-tests-directly-with-test-pl Running regression tests directly with `test.pl`
113113

114114
It can be useful to run a single test folder in isolation. This can be done by
115-
running `test.pl` directly. The way that `test.pl` is run varies between the
115+
running `regression/test.pl` directly. The way that `test.pl` is run varies between the
116116
different modules, and can be ascertained by looking at the `test` target in
117117
the makefile. The simple case is when there isn't a file called `chain.sh`.
118118
Then you can directly run `test.pl` on a single test folder with the
@@ -151,7 +151,7 @@ the end of the run to see how many tests passed, how many failed which were
151151
expected to and how many tests failed which were not expected to.
152152

153153
For more information on the structure of `unit/` and how to tag tests, see
154-
[the section on unit tests in `Compiling.md` in the root of the CBMC
154+
[the section on unit tests in `CODING_STANDARD.md` in the root of the CBMC
155155
repository](https://github.com/diffblue/cbmc/blob/develop/CODING_STANDARD.md#unit-tests)
156156

157157

0 commit comments

Comments
 (0)