diff options
| author | bloodstalker <thabogre@gmail.com> | 2020-03-07 14:52:35 +0000 |
|---|---|---|
| committer | bloodstalker <thabogre@gmail.com> | 2020-03-07 14:52:35 +0000 |
| commit | e6f28490f1def7e31c4ff36a731f584368935e34 (patch) | |
| tree | 74151eff4fe15c1843ecc8eb2f03818828849ffc /README.md | |
| parent | coverage (diff) | |
| download | cgrep-e6f28490f1def7e31c4ff36a731f584368935e34.tar.gz cgrep-e6f28490f1def7e31c4ff36a731f584368935e34.zip | |
more bug fixes as we're getting ready for the first release. still not sure how to handle the test result evaluation.
Diffstat (limited to '')
| -rw-r--r-- | README.md | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -88,6 +88,9 @@ For an up-to-date list, you can run `cgrep --help` or look at the man page. `cgrep` is a clang tool, so it will accept all valid clang command line options. +## Example +You can run the coverage report, `make covrep`, to see some examples. Before running make sure to generate the compilation databases for `cgrep.cpp` and `./test/main.cpp`. The paths need to be right for your system. Please note that even though cgrep's source file is small, the actual code itself isn't. cgrep is clang. So cgrep will be relatively slow in the examples since its running on a Very big codebase. + ## Known Issues `cgrep` will not print out warnings or errors related to the source code so please make sure that clang can successfully build your file before running cgrep on it. |