diff options
| author | Gautham B A <gautham.bangalore@gmail.com> | 2020-12-05 16:11:09 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-12-05 16:11:09 +0530 |
| commit | 626ce00befee975637c7d7795d8d1fce60cea77d (patch) | |
| tree | 41b8ad4d351f598ab33e33f2f4474248cb280a61 | |
| parent | 93748a946684defd1494d5585dbc912e451e83f8 (diff) | |
| download | googletest-626ce00befee975637c7d7795d8d1fce60cea77d.tar.gz googletest-626ce00befee975637c7d7795d8d1fce60cea77d.zip | |
Fix typo
| -rw-r--r-- | googletest/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/googletest/README.md b/googletest/README.md index 9e747ce0..8488aaef 100644 --- a/googletest/README.md +++ b/googletest/README.md @@ -60,7 +60,7 @@ If you want to use GoogleTest in a project which already uses CMake, the easiest way is to get installed libraries and headers. * Import GoogleTest by using `find_package` (or `pkg_check_modules`). For - example, if `find_package(GTest CONFIG REQUIRED)` is succeed, you can use + example, if `find_package(GTest CONFIG REQUIRED)` succeeds, you can use the libraries as `GTest::gtest`, `GTest::gmock`. And a more robust and flexible approach is to build GoogleTest as part of that |
