diff options
| author | Dino Radaković <dinor@google.com> | 2021-04-12 20:14:10 -0700 |
|---|---|---|
| committer | Dino Radaković <dinor@google.com> | 2021-04-12 20:14:10 -0700 |
| commit | ec7fa96f2952088aaed1ec0e63a0011befaabb95 (patch) | |
| tree | e1ad9b9ec9811d77d99c2b9c28d28d9ee0bb78eb | |
| parent | 965f8ecbfd8b91bbd4f5ee4914c028660bb89029 (diff) | |
| parent | 626ce00befee975637c7d7795d8d1fce60cea77d (diff) | |
| download | googletest-ec7fa96f2952088aaed1ec0e63a0011befaabb95.tar.gz googletest-ec7fa96f2952088aaed1ec0e63a0011befaabb95.zip | |
Merge pull request #3158 from GauthamBanasandra:patch-1
PiperOrigin-RevId: 367681693
| -rw-r--r-- | googletest/README.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/googletest/README.md b/googletest/README.md index 717c8867..a1c3c429 100644 --- a/googletest/README.md +++ b/googletest/README.md @@ -60,8 +60,8 @@ 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 - the libraries as `GTest::gtest`, `GTest::gmock`. + 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 project directly. This is done by making the GoogleTest source code available to |
