Improve the tutorial that may be confusing

This commit is contained in:
Hyuk Myeong 2020-09-15 02:17:23 +09:00
parent a4ab0abb93
commit 7aae2ac34c
2 changed files with 31 additions and 23 deletions

View File

@ -98,7 +98,7 @@ is a VS Code extension allowing to view Google Tests in a tree view, and
run/debug your tests. run/debug your tests.
[C++ TestMate](https://github.com/matepek/vscode-catch2-test-adapter) is a VS [C++ TestMate](https://github.com/matepek/vscode-catch2-test-adapter) is a VS
Code extension allowing to view Google Tests in a tree view, and run/debug your Code extension allowing to view Google Test in a tree view, and run/debug your
tests. tests.
[Cornichon](https://pypi.org/project/cornichon/) is a small Gherkin DSL parser [Cornichon](https://pypi.org/project/cornichon/) is a small Gherkin DSL parser

View File

@ -24,17 +24,20 @@ another project.
When building Google Test as a standalone project, the typical workflow starts When building Google Test as a standalone project, the typical workflow starts
with: with:
mkdir mybuild # Create a directory to hold the build output. git clone https://github.com/google/googletest.git -b release-1.10.0
cd mybuild cd googletest
cmake ${GTEST_DIR} # Generate native build scripts. mkdir build # Create a directory to hold the build output.
cd build
If you want to build Google Test's samples, you should replace the last command cmake .. # Generate native build scripts for Google Test
with
cmake -Dgtest_build_samples=ON ${GTEST_DIR}
If you are on a \*nix system, you should now see a Makefile in the current If you are on a \*nix system, you should now see a Makefile in the current
directory. Just type 'make' to build gtest. directory. Just type `make` to build gtest.
make
And if you are a system administrator, you can simply install Google Test.
sudo make install # Install in /usr/local/ by default
If you use Windows and have Visual Studio installed, a `gtest.sln` file and If you use Windows and have Visual Studio installed, a `gtest.sln` file and
several `.vcproj` files will be created. You can then build them using Visual several `.vcproj` files will be created. You can then build them using Visual
@ -44,13 +47,18 @@ On Mac OS X with Xcode installed, a `.xcodeproj` file will be generated.
#### Incorporating Into An Existing CMake Project #### Incorporating Into An Existing CMake Project
If you want to use gtest in a project which already uses CMake, then a more The easiest way to use Google Test is importing installed libraries and headers.
robust and flexible approach is to build gtest as part of that project directly.
This is done by making the GoogleTest source code available to the main build * Import Google Test by using `find_package` (or `pkg_check_modules`).
and adding it using CMake's `add_subdirectory()` command. This has the For example, if `find_package(GTest CONFIG REQUIRED)` is succeed,
significant advantage that the same compiler and linker settings are used you can use the libraries as `GTest::gtest`, `GTest::gmock`.
between gtest and the rest of your project, so issues associated with using
incompatible libraries (eg debug/release), etc. are avoided. This is And a more robust and flexible approach is to build gtest as part of that project
directly. This is done by making the Google Test source code available to the
main build and adding it using CMake's `add_subdirectory()` command.
This has the significant advantage that the same compiler and linker settings
are used between gtest and the rest of your project, so issues associated with
using incompatible libraries (eg debug/release), etc. are avoided. This is
particularly useful on Windows. Making Google Test's source code available to the particularly useful on Windows. Making Google Test's source code available to the
main build can be done a few different ways: main build can be done a few different ways: