![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.10.9006 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2024-07-26 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Audrow Nash
Authors
- Dirk Thomas
- Michel Hidalgo
Generic Build Instructions
Setup
To build Google Test and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build with CMake
Google Test comes with a CMake build script ( CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build Google Test as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building Google Test as a standalone project, the typical workflow starts with:
mkdir mybuild # Create a directory to hold the build output.
cd mybuild
cmake ${GTEST_DIR} # Generate native build scripts.
If you want to build Google Test’s samples, you should replace the last command with
cmake -Dgtest_build_samples=ON ${GTEST_DIR}
If you are on a *nix system, you should now see a Makefile in the current directory. Just type ‘make’ to build gtest.
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
If you want to use gtest in a project which already uses CMake, then a more
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
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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
- Embed the GoogleTest source code as a direct copy in the main project’s source tree. This is often the simplest approach, but is also the hardest to keep up to date. Some organizations may not permit this method.
- Add GoogleTest as a git submodule or equivalent. This may not always be possible or appropriate. Git submodules, for example, have their own set of advantages and drawbacks.
- Use CMake to download GoogleTest as part of the build’s configure step. This is just a little more complex, but doesn’t have the limitations of the other methods.
The last of the above methods is implemented with a small piece of CMake code in
a separate file (e.g. CMakeLists.txt.in
) which is copied to the build area and
then invoked as a sub-build during the CMake stage. That directory is then
pulled into the main build with add_subdirectory()
. For example:
New file CMakeLists.txt.in
:
cmake_minimum_required(VERSION 2.8.2)
project(googletest-download NONE)
include(ExternalProject)
ExternalProject_Add(googletest
GIT_REPOSITORY https://github.com/google/googletest.git
GIT_TAG master
SOURCE_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-src"
BINARY_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-build"
CONFIGURE_COMMAND ""
BUILD_COMMAND ""
INSTALL_COMMAND ""
TEST_COMMAND ""
)
Existing build’s CMakeLists.txt
:
```cmake
Download and unpack googletest at configure time
configure_file(CMakeLists.txt.in googletest-download/CMakeLists.txt) execute_process(COMMAND ${CMAKE_COMMAND} -G “${CMAKE_GENERATOR}” .
File truncated at 100 lines see the full file
Wiki Tutorials
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.14.9000 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | jazzy |
Last Updated | 2024-02-09 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Scott K Logan
Authors
- Audrow Nash
- Dirk Thomas
- Michel Hidalgo
Generic Build Instructions
Setup
To build GoogleTest and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build with CMake
GoogleTest comes with a CMake build script (CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build GoogleTest as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building GoogleTest as a standalone project, the typical workflow starts with
git clone https://github.com/google/googletest.git -b v1.13.0
cd googletest # Main directory of the cloned repository.
mkdir build # Create a directory to hold the build output.
cd build
cmake .. # Generate native build scripts for GoogleTest.
The above command also includes GoogleMock by default. And so, if you want to build only GoogleTest, you should replace the last command with
cmake .. -DBUILD_GMOCK=OFF
If you are on a *nix system, you should now see a Makefile in the current
directory. Just type make
to build GoogleTest. And then you can simply install
GoogleTest if you are a system administrator.
make
sudo make install # Install in /usr/local/ by default
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
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
(orpkg_check_modules
). For example, iffind_package(GTest CONFIG REQUIRED)
succeeds, you can use the libraries asGTest::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
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 GoogleTest 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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
- Embed the GoogleTest source code as a direct copy in the main project’s source tree. This is often the simplest approach, but is also the hardest to keep up to date. Some organizations may not permit this method.
- Add GoogleTest as a git submodule or equivalent. This may not always be possible or appropriate. Git submodules, for example, have their own set of advantages and drawbacks.
- Use CMake to download GoogleTest as part of the build’s configure step. This approach doesn’t have the limitations of the other methods.
The last of the above methods is implemented with a small piece of CMake code that downloads and pulls the GoogleTest code into the main build.
Just add to your CMakeLists.txt
:
```cmake include(FetchContent) FetchContent_Declare( googletest # Specify the commit you depend on and update it regularly. URL https://github.com/google/googletest/archive/5376968f6948923e2411081fd9372e71a59d8e77.zip )
For Windows: Prevent overriding the parent project’s compiler/linker settings
set(gtest_force_shared_crt ON CACHE BOOL “” FORCE)
File truncated at 100 lines see the full file
Wiki Tutorials
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.15.1 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | kilted |
Last Updated | 2025-04-18 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Scott K Logan
Authors
- Audrow Nash
- Dirk Thomas
- Michel Hidalgo
Generic Build Instructions
Setup
To build GoogleTest and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build with CMake
GoogleTest comes with a CMake build script (CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build GoogleTest as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building GoogleTest as a standalone project, the typical workflow starts with
git clone https://github.com/google/googletest.git -b v1.13.0
cd googletest # Main directory of the cloned repository.
mkdir build # Create a directory to hold the build output.
cd build
cmake .. # Generate native build scripts for GoogleTest.
The above command also includes GoogleMock by default. And so, if you want to build only GoogleTest, you should replace the last command with
cmake .. -DBUILD_GMOCK=OFF
If you are on a *nix system, you should now see a Makefile in the current
directory. Just type make
to build GoogleTest. And then you can simply install
GoogleTest if you are a system administrator.
make
sudo make install # Install in /usr/local/ by default
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
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
(orpkg_check_modules
). For example, iffind_package(GTest CONFIG REQUIRED)
succeeds, you can use the libraries asGTest::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
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 GoogleTest 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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
- Embed the GoogleTest source code as a direct copy in the main project’s source tree. This is often the simplest approach, but is also the hardest to keep up to date. Some organizations may not permit this method.
- Add GoogleTest as a git submodule or equivalent. This may not always be possible or appropriate. Git submodules, for example, have their own set of advantages and drawbacks.
- Use CMake to download GoogleTest as part of the build’s configure step. This approach doesn’t have the limitations of the other methods.
The last of the above methods is implemented with a small piece of CMake code that downloads and pulls the GoogleTest code into the main build.
Just add to your CMakeLists.txt
:
```cmake include(FetchContent) FetchContent_Declare( googletest # Specify the commit you depend on and update it regularly. URL https://github.com/google/googletest/archive/5376968f6948923e2411081fd9372e71a59d8e77.zip )
For Windows: Prevent overriding the parent project’s compiler/linker settings
set(gtest_force_shared_crt ON CACHE BOOL “” FORCE)
File truncated at 100 lines see the full file
Changelog for package gtest_vendor
1.15.1 (2025-04-18)
- Bump minimum CMake version to 3.15 (#33)
- Contributors: mosfet80
1.15.0 (2024-04-26)
Wiki Tutorials
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.16.0 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | rolling |
Last Updated | 2025-04-24 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Scott K Logan
Authors
- Audrow Nash
- Dirk Thomas
- Michel Hidalgo
Generic Build Instructions
Setup
To build GoogleTest and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build with CMake
GoogleTest comes with a CMake build script (CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build GoogleTest as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building GoogleTest as a standalone project, the typical workflow starts with
git clone https://github.com/google/googletest.git -b v1.13.0
cd googletest # Main directory of the cloned repository.
mkdir build # Create a directory to hold the build output.
cd build
cmake .. # Generate native build scripts for GoogleTest.
The above command also includes GoogleMock by default. And so, if you want to build only GoogleTest, you should replace the last command with
cmake .. -DBUILD_GMOCK=OFF
If you are on a *nix system, you should now see a Makefile in the current
directory. Just type make
to build GoogleTest. And then you can simply install
GoogleTest if you are a system administrator.
make
sudo make install # Install in /usr/local/ by default
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
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
(orpkg_check_modules
). For example, iffind_package(GTest CONFIG REQUIRED)
succeeds, you can use the libraries asGTest::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
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 GoogleTest 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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
- Embed the GoogleTest source code as a direct copy in the main project’s source tree. This is often the simplest approach, but is also the hardest to keep up to date. Some organizations may not permit this method.
- Add GoogleTest as a git submodule or equivalent. This may not always be possible or appropriate. Git submodules, for example, have their own set of advantages and drawbacks.
- Use CMake to download GoogleTest as part of the build’s configure step. This approach doesn’t have the limitations of the other methods.
The last of the above methods is implemented with a small piece of CMake code that downloads and pulls the GoogleTest code into the main build.
Just add to your CMakeLists.txt
:
```cmake include(FetchContent) FetchContent_Declare( googletest # Specify the commit you depend on and update it regularly. URL https://github.com/google/googletest/archive/5376968f6948923e2411081fd9372e71a59d8e77.zip )
For Windows: Prevent overriding the parent project’s compiler/linker settings
set(gtest_force_shared_crt ON CACHE BOOL “” FORCE)
File truncated at 100 lines see the full file
Changelog for package gtest_vendor
1.16.0 (2025-04-24)
1.15.1 (2025-04-18)
- Bump minimum CMake version to 3.15 (#33)
- Contributors: mosfet80
1.15.0 (2024-04-26)
Wiki Tutorials
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.8.0 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | ardent |
Last Updated | 2017-08-08 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Dirk Thomas
Authors
Generic Build Instructions
Setup
To build Google Test and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build
Suppose you put Google Test in directory ${GTEST_DIR}
. To build it,
create a library build target (or a project as called by Visual Studio
and Xcode) to compile
${GTEST_DIR}/src/gtest-all.cc
with ${GTEST_DIR}/include
in the system header search path and ${GTEST_DIR}
in the normal header search path. Assuming a Linux-like system and gcc,
something like the following will do:
g++ -isystem ${GTEST_DIR}/include -I${GTEST_DIR} \
-pthread -c ${GTEST_DIR}/src/gtest-all.cc
ar -rv libgtest.a gtest-all.o
(We need -pthread
as Google Test uses threads.)
Next, you should compile your test source file with
${GTEST_DIR}/include
in the system header search path, and link it
with gtest and any other necessary libraries:
g++ -isystem ${GTEST_DIR}/include -pthread path/to/your_test.cc libgtest.a \
-o your_test
As an example, the make/ directory contains a Makefile that you can use to build Google Test on systems where GNU make is available (e.g. Linux, Mac OS X, and Cygwin). It doesn’t try to build Google Test’s own tests. Instead, it just builds the Google Test library and a sample test. You can use it as a starting point for your own build script.
If the default settings are correct for your environment, the following commands should succeed:
cd ${GTEST_DIR}/make
make
./sample1_unittest
If you see errors, try to tweak the contents of make/Makefile
to make
them go away. There are instructions in make/Makefile
on how to do
it.
Using CMake
Google Test comes with a CMake build script ( CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. The typical workflow starts with:
mkdir mybuild # Create a directory to hold the build output.
cd mybuild
cmake ${GTEST_DIR} # Generate native build scripts.
If you want to build Google Test’s samples, you should replace the last command with
cmake -Dgtest_build_samples=ON ${GTEST_DIR}
If you are on a *nix system, you should now see a Makefile in the current directory. Just type ‘make’ to build gtest.
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 Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Legacy Build Scripts
Before settling on CMake, we have been providing hand-maintained build projects/scripts for Visual Studio, Xcode, and Autotools. While we continue to provide them for convenience, they are not actively maintained any more. We highly recommend that you follow the instructions in the previous two sections to integrate Google Test with your existing build system.
If you still need to use the legacy build scripts, here’s how:
The msvc\ folder contains two solutions with Visual C++ projects.
Open the gtest.sln
or gtest-md.sln
file using Visual Studio, and you
are ready to build Google Test the same way you build any Visual
Studio project. Files that have names ending with -md use DLL
versions of Microsoft runtime libraries (the /MD or the /MDd compiler
option). Files without that suffix use static versions of the runtime
libraries (the /MT or the /MTd option). Please note that one must use
File truncated at 100 lines see the full file
Wiki Tutorials
Dependant Packages
Name | Deps |
---|---|
ament_cmake_gtest | |
gmock_vendor |
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.15.0 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | ros2 |
Last Updated | 2024-04-26 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Scott K Logan
Authors
- Audrow Nash
- Dirk Thomas
- Michel Hidalgo
Generic Build Instructions
Setup
To build GoogleTest and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build with CMake
GoogleTest comes with a CMake build script (CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build GoogleTest as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building GoogleTest as a standalone project, the typical workflow starts with
git clone https://github.com/google/googletest.git -b v1.13.0
cd googletest # Main directory of the cloned repository.
mkdir build # Create a directory to hold the build output.
cd build
cmake .. # Generate native build scripts for GoogleTest.
The above command also includes GoogleMock by default. And so, if you want to build only GoogleTest, you should replace the last command with
cmake .. -DBUILD_GMOCK=OFF
If you are on a *nix system, you should now see a Makefile in the current
directory. Just type make
to build GoogleTest. And then you can simply install
GoogleTest if you are a system administrator.
make
sudo make install # Install in /usr/local/ by default
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
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
(orpkg_check_modules
). For example, iffind_package(GTest CONFIG REQUIRED)
succeeds, you can use the libraries asGTest::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
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 GoogleTest 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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
- Embed the GoogleTest source code as a direct copy in the main project’s source tree. This is often the simplest approach, but is also the hardest to keep up to date. Some organizations may not permit this method.
- Add GoogleTest as a git submodule or equivalent. This may not always be possible or appropriate. Git submodules, for example, have their own set of advantages and drawbacks.
- Use CMake to download GoogleTest as part of the build’s configure step. This approach doesn’t have the limitations of the other methods.
The last of the above methods is implemented with a small piece of CMake code that downloads and pulls the GoogleTest code into the main build.
Just add to your CMakeLists.txt
:
```cmake include(FetchContent) FetchContent_Declare( googletest # Specify the commit you depend on and update it regularly. URL https://github.com/google/googletest/archive/5376968f6948923e2411081fd9372e71a59d8e77.zip )
For Windows: Prevent overriding the parent project’s compiler/linker settings
set(gtest_force_shared_crt ON CACHE BOOL “” FORCE)
File truncated at 100 lines see the full file
Changelog for package gtest_vendor
1.15.0 (2024-04-26)
Wiki Tutorials
Dependant Packages
Name | Deps |
---|---|
ament_cmake_gtest | |
gmock_vendor |
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.8.0 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | crystal |
Last Updated | 2019-01-04 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Dirk Thomas
Authors
Generic Build Instructions
Setup
To build Google Test and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build
Suppose you put Google Test in directory ${GTEST_DIR}
. To build it,
create a library build target (or a project as called by Visual Studio
and Xcode) to compile
${GTEST_DIR}/src/gtest-all.cc
with ${GTEST_DIR}/include
in the system header search path and ${GTEST_DIR}
in the normal header search path. Assuming a Linux-like system and gcc,
something like the following will do:
g++ -isystem ${GTEST_DIR}/include -I${GTEST_DIR} \
-pthread -c ${GTEST_DIR}/src/gtest-all.cc
ar -rv libgtest.a gtest-all.o
(We need -pthread
as Google Test uses threads.)
Next, you should compile your test source file with
${GTEST_DIR}/include
in the system header search path, and link it
with gtest and any other necessary libraries:
g++ -isystem ${GTEST_DIR}/include -pthread path/to/your_test.cc libgtest.a \
-o your_test
As an example, the make/ directory contains a Makefile that you can use to build Google Test on systems where GNU make is available (e.g. Linux, Mac OS X, and Cygwin). It doesn’t try to build Google Test’s own tests. Instead, it just builds the Google Test library and a sample test. You can use it as a starting point for your own build script.
If the default settings are correct for your environment, the following commands should succeed:
cd ${GTEST_DIR}/make
make
./sample1_unittest
If you see errors, try to tweak the contents of make/Makefile
to make
them go away. There are instructions in make/Makefile
on how to do
it.
Using CMake
Google Test comes with a CMake build script ( CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build Google Test as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building Google Test as a standalone project, the typical workflow starts with:
mkdir mybuild # Create a directory to hold the build output.
cd mybuild
cmake ${GTEST_DIR} # Generate native build scripts.
If you want to build Google Test’s samples, you should replace the last command with
cmake -Dgtest_build_samples=ON ${GTEST_DIR}
If you are on a *nix system, you should now see a Makefile in the current directory. Just type ‘make’ to build gtest.
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 Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
If you want to use gtest in a project which already uses CMake, then a
more 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 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 GoogleTest’s source code available to the
main build can be done a few different ways:
File truncated at 100 lines see the full file
Wiki Tutorials
Dependant Packages
Name | Deps |
---|---|
ament_cmake_gtest | |
gmock_vendor |
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.15.0 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | ros2 |
Last Updated | 2024-04-26 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Scott K Logan
Authors
- Audrow Nash
- Dirk Thomas
- Michel Hidalgo
Generic Build Instructions
Setup
To build GoogleTest and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build with CMake
GoogleTest comes with a CMake build script (CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build GoogleTest as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building GoogleTest as a standalone project, the typical workflow starts with
git clone https://github.com/google/googletest.git -b v1.13.0
cd googletest # Main directory of the cloned repository.
mkdir build # Create a directory to hold the build output.
cd build
cmake .. # Generate native build scripts for GoogleTest.
The above command also includes GoogleMock by default. And so, if you want to build only GoogleTest, you should replace the last command with
cmake .. -DBUILD_GMOCK=OFF
If you are on a *nix system, you should now see a Makefile in the current
directory. Just type make
to build GoogleTest. And then you can simply install
GoogleTest if you are a system administrator.
make
sudo make install # Install in /usr/local/ by default
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
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
(orpkg_check_modules
). For example, iffind_package(GTest CONFIG REQUIRED)
succeeds, you can use the libraries asGTest::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
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 GoogleTest 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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
- Embed the GoogleTest source code as a direct copy in the main project’s source tree. This is often the simplest approach, but is also the hardest to keep up to date. Some organizations may not permit this method.
- Add GoogleTest as a git submodule or equivalent. This may not always be possible or appropriate. Git submodules, for example, have their own set of advantages and drawbacks.
- Use CMake to download GoogleTest as part of the build’s configure step. This approach doesn’t have the limitations of the other methods.
The last of the above methods is implemented with a small piece of CMake code that downloads and pulls the GoogleTest code into the main build.
Just add to your CMakeLists.txt
:
```cmake include(FetchContent) FetchContent_Declare( googletest # Specify the commit you depend on and update it regularly. URL https://github.com/google/googletest/archive/5376968f6948923e2411081fd9372e71a59d8e77.zip )
For Windows: Prevent overriding the parent project’s compiler/linker settings
set(gtest_force_shared_crt ON CACHE BOOL “” FORCE)
File truncated at 100 lines see the full file
Changelog for package gtest_vendor
1.15.0 (2024-04-26)
Wiki Tutorials
Dependant Packages
Name | Deps |
---|---|
mrt_cmake_modules | |
ament_cmake_gtest | |
gmock_vendor |
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.8.9000 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | dashing |
Last Updated | 2019-05-08 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Dirk Thomas
Authors
Generic Build Instructions
Setup
To build Google Test and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build
Suppose you put Google Test in directory ${GTEST_DIR}
. To build it, create a
library build target (or a project as called by Visual Studio and Xcode) to
compile
${GTEST_DIR}/src/gtest-all.cc
with ${GTEST_DIR}/include
in the system header search path and ${GTEST_DIR}
in the normal header search path. Assuming a Linux-like system and gcc,
something like the following will do:
g++ -std=c++11 -isystem ${GTEST_DIR}/include -I${GTEST_DIR} \
-pthread -c ${GTEST_DIR}/src/gtest-all.cc
ar -rv libgtest.a gtest-all.o
(We need -pthread
as Google Test uses threads.)
Next, you should compile your test source file with ${GTEST_DIR}/include
in
the system header search path, and link it with gtest and any other necessary
libraries:
g++ -std=c++11 -isystem ${GTEST_DIR}/include -pthread path/to/your_test.cc libgtest.a \
-o your_test
As an example, the make/ directory contains a Makefile that you can use to build Google Test on systems where GNU make is available (e.g. Linux, Mac OS X, and Cygwin). It doesn’t try to build Google Test’s own tests. Instead, it just builds the Google Test library and a sample test. You can use it as a starting point for your own build script.
If the default settings are correct for your environment, the following commands should succeed:
cd ${GTEST_DIR}/make
make
./sample1_unittest
If you see errors, try to tweak the contents of make/Makefile
to make them go
away. There are instructions in make/Makefile
on how to do it.
Using CMake
Google Test comes with a CMake build script ( CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build Google Test as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building Google Test as a standalone project, the typical workflow starts with:
mkdir mybuild # Create a directory to hold the build output.
cd mybuild
cmake ${GTEST_DIR} # Generate native build scripts.
If you want to build Google Test’s samples, you should replace the last command with
cmake -Dgtest_build_samples=ON ${GTEST_DIR}
If you are on a *nix system, you should now see a Makefile in the current directory. Just type ‘make’ to build gtest.
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
If you want to use gtest in a project which already uses CMake, then a more
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
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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
File truncated at 100 lines see the full file
Wiki Tutorials
Dependant Packages
Name | Deps |
---|---|
mrt_cmake_modules | |
ament_cmake_gtest | |
gmock_vendor |
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.10.9003 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | galactic |
Last Updated | 2021-06-04 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Michel Hidalgo
Authors
- Dirk Thomas
Generic Build Instructions
Setup
To build Google Test and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build with CMake
Google Test comes with a CMake build script ( CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build Google Test as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building Google Test as a standalone project, the typical workflow starts with:
mkdir mybuild # Create a directory to hold the build output.
cd mybuild
cmake ${GTEST_DIR} # Generate native build scripts.
If you want to build Google Test’s samples, you should replace the last command with
cmake -Dgtest_build_samples=ON ${GTEST_DIR}
If you are on a *nix system, you should now see a Makefile in the current directory. Just type ‘make’ to build gtest.
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
If you want to use gtest in a project which already uses CMake, then a more
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
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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
- Embed the GoogleTest source code as a direct copy in the main project’s source tree. This is often the simplest approach, but is also the hardest to keep up to date. Some organizations may not permit this method.
- Add GoogleTest as a git submodule or equivalent. This may not always be possible or appropriate. Git submodules, for example, have their own set of advantages and drawbacks.
- Use CMake to download GoogleTest as part of the build’s configure step. This is just a little more complex, but doesn’t have the limitations of the other methods.
The last of the above methods is implemented with a small piece of CMake code in
a separate file (e.g. CMakeLists.txt.in
) which is copied to the build area and
then invoked as a sub-build during the CMake stage. That directory is then
pulled into the main build with add_subdirectory()
. For example:
New file CMakeLists.txt.in
:
cmake_minimum_required(VERSION 2.8.2)
project(googletest-download NONE)
include(ExternalProject)
ExternalProject_Add(googletest
GIT_REPOSITORY https://github.com/google/googletest.git
GIT_TAG master
SOURCE_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-src"
BINARY_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-build"
CONFIGURE_COMMAND ""
BUILD_COMMAND ""
INSTALL_COMMAND ""
TEST_COMMAND ""
)
Existing build’s CMakeLists.txt
:
```cmake
Download and unpack googletest at configure time
configure_file(CMakeLists.txt.in googletest-download/CMakeLists.txt) execute_process(COMMAND ${CMAKE_COMMAND} -G “${CMAKE_GENERATOR}” .
File truncated at 100 lines see the full file
Wiki Tutorials
Dependant Packages
Name | Deps |
---|---|
mrt_cmake_modules | |
ament_cmake_gtest | |
gmock_vendor |
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.8.9001 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | foxy |
Last Updated | 2021-08-31 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Dirk Thomas
Authors
Generic Build Instructions
Setup
To build Google Test and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build
Suppose you put Google Test in directory ${GTEST_DIR}
. To build it, create a
library build target (or a project as called by Visual Studio and Xcode) to
compile
${GTEST_DIR}/src/gtest-all.cc
with ${GTEST_DIR}/include
in the system header search path and ${GTEST_DIR}
in the normal header search path. Assuming a Linux-like system and gcc,
something like the following will do:
g++ -std=c++11 -isystem ${GTEST_DIR}/include -I${GTEST_DIR} \
-pthread -c ${GTEST_DIR}/src/gtest-all.cc
ar -rv libgtest.a gtest-all.o
(We need -pthread
as Google Test uses threads.)
Next, you should compile your test source file with ${GTEST_DIR}/include
in
the system header search path, and link it with gtest and any other necessary
libraries:
g++ -std=c++11 -isystem ${GTEST_DIR}/include -pthread path/to/your_test.cc libgtest.a \
-o your_test
As an example, the make/ directory contains a Makefile that you can use to build Google Test on systems where GNU make is available (e.g. Linux, Mac OS X, and Cygwin). It doesn’t try to build Google Test’s own tests. Instead, it just builds the Google Test library and a sample test. You can use it as a starting point for your own build script.
If the default settings are correct for your environment, the following commands should succeed:
cd ${GTEST_DIR}/make
make
./sample1_unittest
If you see errors, try to tweak the contents of make/Makefile
to make them go
away. There are instructions in make/Makefile
on how to do it.
Using CMake
Google Test comes with a CMake build script ( CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build Google Test as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building Google Test as a standalone project, the typical workflow starts with:
mkdir mybuild # Create a directory to hold the build output.
cd mybuild
cmake ${GTEST_DIR} # Generate native build scripts.
If you want to build Google Test’s samples, you should replace the last command with
cmake -Dgtest_build_samples=ON ${GTEST_DIR}
If you are on a *nix system, you should now see a Makefile in the current directory. Just type ‘make’ to build gtest.
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
If you want to use gtest in a project which already uses CMake, then a more
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
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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
File truncated at 100 lines see the full file
Wiki Tutorials
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.10.9005 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | iron |
Last Updated | 2023-04-11 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Scott K Logan
Authors
- Audrow Nash
- Dirk Thomas
- Michel Hidalgo
Generic Build Instructions
Setup
To build Google Test and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build with CMake
Google Test comes with a CMake build script ( CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build Google Test as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building Google Test as a standalone project, the typical workflow starts with:
mkdir mybuild # Create a directory to hold the build output.
cd mybuild
cmake ${GTEST_DIR} # Generate native build scripts.
If you want to build Google Test’s samples, you should replace the last command with
cmake -Dgtest_build_samples=ON ${GTEST_DIR}
If you are on a *nix system, you should now see a Makefile in the current directory. Just type ‘make’ to build gtest.
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
If you want to use gtest in a project which already uses CMake, then a more
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
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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
- Embed the GoogleTest source code as a direct copy in the main project’s source tree. This is often the simplest approach, but is also the hardest to keep up to date. Some organizations may not permit this method.
- Add GoogleTest as a git submodule or equivalent. This may not always be possible or appropriate. Git submodules, for example, have their own set of advantages and drawbacks.
- Use CMake to download GoogleTest as part of the build’s configure step. This is just a little more complex, but doesn’t have the limitations of the other methods.
The last of the above methods is implemented with a small piece of CMake code in
a separate file (e.g. CMakeLists.txt.in
) which is copied to the build area and
then invoked as a sub-build during the CMake stage. That directory is then
pulled into the main build with add_subdirectory()
. For example:
New file CMakeLists.txt.in
:
cmake_minimum_required(VERSION 2.8.2)
project(googletest-download NONE)
include(ExternalProject)
ExternalProject_Add(googletest
GIT_REPOSITORY https://github.com/google/googletest.git
GIT_TAG master
SOURCE_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-src"
BINARY_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-build"
CONFIGURE_COMMAND ""
BUILD_COMMAND ""
INSTALL_COMMAND ""
TEST_COMMAND ""
)
Existing build’s CMakeLists.txt
:
```cmake
Download and unpack googletest at configure time
configure_file(CMakeLists.txt.in googletest-download/CMakeLists.txt) execute_process(COMMAND ${CMAKE_COMMAND} -G “${CMAKE_GENERATOR}” .
File truncated at 100 lines see the full file
Wiki Tutorials
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.10.9006 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2024-07-26 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Audrow Nash
Authors
- Dirk Thomas
- Michel Hidalgo
Generic Build Instructions
Setup
To build Google Test and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build with CMake
Google Test comes with a CMake build script ( CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build Google Test as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building Google Test as a standalone project, the typical workflow starts with:
mkdir mybuild # Create a directory to hold the build output.
cd mybuild
cmake ${GTEST_DIR} # Generate native build scripts.
If you want to build Google Test’s samples, you should replace the last command with
cmake -Dgtest_build_samples=ON ${GTEST_DIR}
If you are on a *nix system, you should now see a Makefile in the current directory. Just type ‘make’ to build gtest.
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
If you want to use gtest in a project which already uses CMake, then a more
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
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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
- Embed the GoogleTest source code as a direct copy in the main project’s source tree. This is often the simplest approach, but is also the hardest to keep up to date. Some organizations may not permit this method.
- Add GoogleTest as a git submodule or equivalent. This may not always be possible or appropriate. Git submodules, for example, have their own set of advantages and drawbacks.
- Use CMake to download GoogleTest as part of the build’s configure step. This is just a little more complex, but doesn’t have the limitations of the other methods.
The last of the above methods is implemented with a small piece of CMake code in
a separate file (e.g. CMakeLists.txt.in
) which is copied to the build area and
then invoked as a sub-build during the CMake stage. That directory is then
pulled into the main build with add_subdirectory()
. For example:
New file CMakeLists.txt.in
:
cmake_minimum_required(VERSION 2.8.2)
project(googletest-download NONE)
include(ExternalProject)
ExternalProject_Add(googletest
GIT_REPOSITORY https://github.com/google/googletest.git
GIT_TAG master
SOURCE_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-src"
BINARY_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-build"
CONFIGURE_COMMAND ""
BUILD_COMMAND ""
INSTALL_COMMAND ""
TEST_COMMAND ""
)
Existing build’s CMakeLists.txt
:
```cmake
Download and unpack googletest at configure time
configure_file(CMakeLists.txt.in googletest-download/CMakeLists.txt) execute_process(COMMAND ${CMAKE_COMMAND} -G “${CMAKE_GENERATOR}” .
File truncated at 100 lines see the full file
Wiki Tutorials
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.10.9006 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2024-07-26 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Audrow Nash
Authors
- Dirk Thomas
- Michel Hidalgo
Generic Build Instructions
Setup
To build Google Test and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build with CMake
Google Test comes with a CMake build script ( CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build Google Test as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building Google Test as a standalone project, the typical workflow starts with:
mkdir mybuild # Create a directory to hold the build output.
cd mybuild
cmake ${GTEST_DIR} # Generate native build scripts.
If you want to build Google Test’s samples, you should replace the last command with
cmake -Dgtest_build_samples=ON ${GTEST_DIR}
If you are on a *nix system, you should now see a Makefile in the current directory. Just type ‘make’ to build gtest.
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
If you want to use gtest in a project which already uses CMake, then a more
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
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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
- Embed the GoogleTest source code as a direct copy in the main project’s source tree. This is often the simplest approach, but is also the hardest to keep up to date. Some organizations may not permit this method.
- Add GoogleTest as a git submodule or equivalent. This may not always be possible or appropriate. Git submodules, for example, have their own set of advantages and drawbacks.
- Use CMake to download GoogleTest as part of the build’s configure step. This is just a little more complex, but doesn’t have the limitations of the other methods.
The last of the above methods is implemented with a small piece of CMake code in
a separate file (e.g. CMakeLists.txt.in
) which is copied to the build area and
then invoked as a sub-build during the CMake stage. That directory is then
pulled into the main build with add_subdirectory()
. For example:
New file CMakeLists.txt.in
:
cmake_minimum_required(VERSION 2.8.2)
project(googletest-download NONE)
include(ExternalProject)
ExternalProject_Add(googletest
GIT_REPOSITORY https://github.com/google/googletest.git
GIT_TAG master
SOURCE_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-src"
BINARY_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-build"
CONFIGURE_COMMAND ""
BUILD_COMMAND ""
INSTALL_COMMAND ""
TEST_COMMAND ""
)
Existing build’s CMakeLists.txt
:
```cmake
Download and unpack googletest at configure time
configure_file(CMakeLists.txt.in googletest-download/CMakeLists.txt) execute_process(COMMAND ${CMAKE_COMMAND} -G “${CMAKE_GENERATOR}” .
File truncated at 100 lines see the full file
Wiki Tutorials
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.10.9006 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2024-07-26 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Audrow Nash
Authors
- Dirk Thomas
- Michel Hidalgo
Generic Build Instructions
Setup
To build Google Test and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build with CMake
Google Test comes with a CMake build script ( CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build Google Test as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building Google Test as a standalone project, the typical workflow starts with:
mkdir mybuild # Create a directory to hold the build output.
cd mybuild
cmake ${GTEST_DIR} # Generate native build scripts.
If you want to build Google Test’s samples, you should replace the last command with
cmake -Dgtest_build_samples=ON ${GTEST_DIR}
If you are on a *nix system, you should now see a Makefile in the current directory. Just type ‘make’ to build gtest.
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
If you want to use gtest in a project which already uses CMake, then a more
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
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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
- Embed the GoogleTest source code as a direct copy in the main project’s source tree. This is often the simplest approach, but is also the hardest to keep up to date. Some organizations may not permit this method.
- Add GoogleTest as a git submodule or equivalent. This may not always be possible or appropriate. Git submodules, for example, have their own set of advantages and drawbacks.
- Use CMake to download GoogleTest as part of the build’s configure step. This is just a little more complex, but doesn’t have the limitations of the other methods.
The last of the above methods is implemented with a small piece of CMake code in
a separate file (e.g. CMakeLists.txt.in
) which is copied to the build area and
then invoked as a sub-build during the CMake stage. That directory is then
pulled into the main build with add_subdirectory()
. For example:
New file CMakeLists.txt.in
:
cmake_minimum_required(VERSION 2.8.2)
project(googletest-download NONE)
include(ExternalProject)
ExternalProject_Add(googletest
GIT_REPOSITORY https://github.com/google/googletest.git
GIT_TAG master
SOURCE_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-src"
BINARY_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-build"
CONFIGURE_COMMAND ""
BUILD_COMMAND ""
INSTALL_COMMAND ""
TEST_COMMAND ""
)
Existing build’s CMakeLists.txt
:
```cmake
Download and unpack googletest at configure time
configure_file(CMakeLists.txt.in googletest-download/CMakeLists.txt) execute_process(COMMAND ${CMAKE_COMMAND} -G “${CMAKE_GENERATOR}” .
File truncated at 100 lines see the full file
Wiki Tutorials
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.10.9006 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2024-07-26 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Audrow Nash
Authors
- Dirk Thomas
- Michel Hidalgo
Generic Build Instructions
Setup
To build Google Test and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build with CMake
Google Test comes with a CMake build script ( CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build Google Test as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building Google Test as a standalone project, the typical workflow starts with:
mkdir mybuild # Create a directory to hold the build output.
cd mybuild
cmake ${GTEST_DIR} # Generate native build scripts.
If you want to build Google Test’s samples, you should replace the last command with
cmake -Dgtest_build_samples=ON ${GTEST_DIR}
If you are on a *nix system, you should now see a Makefile in the current directory. Just type ‘make’ to build gtest.
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
If you want to use gtest in a project which already uses CMake, then a more
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
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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
- Embed the GoogleTest source code as a direct copy in the main project’s source tree. This is often the simplest approach, but is also the hardest to keep up to date. Some organizations may not permit this method.
- Add GoogleTest as a git submodule or equivalent. This may not always be possible or appropriate. Git submodules, for example, have their own set of advantages and drawbacks.
- Use CMake to download GoogleTest as part of the build’s configure step. This is just a little more complex, but doesn’t have the limitations of the other methods.
The last of the above methods is implemented with a small piece of CMake code in
a separate file (e.g. CMakeLists.txt.in
) which is copied to the build area and
then invoked as a sub-build during the CMake stage. That directory is then
pulled into the main build with add_subdirectory()
. For example:
New file CMakeLists.txt.in
:
cmake_minimum_required(VERSION 2.8.2)
project(googletest-download NONE)
include(ExternalProject)
ExternalProject_Add(googletest
GIT_REPOSITORY https://github.com/google/googletest.git
GIT_TAG master
SOURCE_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-src"
BINARY_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-build"
CONFIGURE_COMMAND ""
BUILD_COMMAND ""
INSTALL_COMMAND ""
TEST_COMMAND ""
)
Existing build’s CMakeLists.txt
:
```cmake
Download and unpack googletest at configure time
configure_file(CMakeLists.txt.in googletest-download/CMakeLists.txt) execute_process(COMMAND ${CMAKE_COMMAND} -G “${CMAKE_GENERATOR}” .
File truncated at 100 lines see the full file
Wiki Tutorials
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.10.9006 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2024-07-26 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Audrow Nash
Authors
- Dirk Thomas
- Michel Hidalgo
Generic Build Instructions
Setup
To build Google Test and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build with CMake
Google Test comes with a CMake build script ( CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build Google Test as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building Google Test as a standalone project, the typical workflow starts with:
mkdir mybuild # Create a directory to hold the build output.
cd mybuild
cmake ${GTEST_DIR} # Generate native build scripts.
If you want to build Google Test’s samples, you should replace the last command with
cmake -Dgtest_build_samples=ON ${GTEST_DIR}
If you are on a *nix system, you should now see a Makefile in the current directory. Just type ‘make’ to build gtest.
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
If you want to use gtest in a project which already uses CMake, then a more
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
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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
- Embed the GoogleTest source code as a direct copy in the main project’s source tree. This is often the simplest approach, but is also the hardest to keep up to date. Some organizations may not permit this method.
- Add GoogleTest as a git submodule or equivalent. This may not always be possible or appropriate. Git submodules, for example, have their own set of advantages and drawbacks.
- Use CMake to download GoogleTest as part of the build’s configure step. This is just a little more complex, but doesn’t have the limitations of the other methods.
The last of the above methods is implemented with a small piece of CMake code in
a separate file (e.g. CMakeLists.txt.in
) which is copied to the build area and
then invoked as a sub-build during the CMake stage. That directory is then
pulled into the main build with add_subdirectory()
. For example:
New file CMakeLists.txt.in
:
cmake_minimum_required(VERSION 2.8.2)
project(googletest-download NONE)
include(ExternalProject)
ExternalProject_Add(googletest
GIT_REPOSITORY https://github.com/google/googletest.git
GIT_TAG master
SOURCE_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-src"
BINARY_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-build"
CONFIGURE_COMMAND ""
BUILD_COMMAND ""
INSTALL_COMMAND ""
TEST_COMMAND ""
)
Existing build’s CMakeLists.txt
:
```cmake
Download and unpack googletest at configure time
configure_file(CMakeLists.txt.in googletest-download/CMakeLists.txt) execute_process(COMMAND ${CMAKE_COMMAND} -G “${CMAKE_GENERATOR}” .
File truncated at 100 lines see the full file
Wiki Tutorials
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.10.9006 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2024-07-26 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Audrow Nash
Authors
- Dirk Thomas
- Michel Hidalgo
Generic Build Instructions
Setup
To build Google Test and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build with CMake
Google Test comes with a CMake build script ( CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build Google Test as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building Google Test as a standalone project, the typical workflow starts with:
mkdir mybuild # Create a directory to hold the build output.
cd mybuild
cmake ${GTEST_DIR} # Generate native build scripts.
If you want to build Google Test’s samples, you should replace the last command with
cmake -Dgtest_build_samples=ON ${GTEST_DIR}
If you are on a *nix system, you should now see a Makefile in the current directory. Just type ‘make’ to build gtest.
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
If you want to use gtest in a project which already uses CMake, then a more
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
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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
- Embed the GoogleTest source code as a direct copy in the main project’s source tree. This is often the simplest approach, but is also the hardest to keep up to date. Some organizations may not permit this method.
- Add GoogleTest as a git submodule or equivalent. This may not always be possible or appropriate. Git submodules, for example, have their own set of advantages and drawbacks.
- Use CMake to download GoogleTest as part of the build’s configure step. This is just a little more complex, but doesn’t have the limitations of the other methods.
The last of the above methods is implemented with a small piece of CMake code in
a separate file (e.g. CMakeLists.txt.in
) which is copied to the build area and
then invoked as a sub-build during the CMake stage. That directory is then
pulled into the main build with add_subdirectory()
. For example:
New file CMakeLists.txt.in
:
cmake_minimum_required(VERSION 2.8.2)
project(googletest-download NONE)
include(ExternalProject)
ExternalProject_Add(googletest
GIT_REPOSITORY https://github.com/google/googletest.git
GIT_TAG master
SOURCE_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-src"
BINARY_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-build"
CONFIGURE_COMMAND ""
BUILD_COMMAND ""
INSTALL_COMMAND ""
TEST_COMMAND ""
)
Existing build’s CMakeLists.txt
:
```cmake
Download and unpack googletest at configure time
configure_file(CMakeLists.txt.in googletest-download/CMakeLists.txt) execute_process(COMMAND ${CMAKE_COMMAND} -G “${CMAKE_GENERATOR}” .
File truncated at 100 lines see the full file
Wiki Tutorials
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged gtest_vendor at Robotics Stack Exchange
![]() |
gtest_vendor package from googletest repogmock_vendor gtest_vendor |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.10.9006 |
License | BSD |
Build type | CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ament/googletest.git |
VCS Type | git |
VCS Version | humble |
Last Updated | 2024-07-26 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Audrow Nash
Authors
- Dirk Thomas
- Michel Hidalgo
Generic Build Instructions
Setup
To build Google Test and your tests that use it, you need to tell your build system where to find its headers and source files. The exact way to do it depends on which build system you use, and is usually straightforward.
Build with CMake
Google Test comes with a CMake build script ( CMakeLists.txt) that can be used on a wide range of platforms (“C” stands for cross-platform.). If you don’t have CMake installed already, you can download it for free from http://www.cmake.org/.
CMake works by generating native makefiles or build projects that can be used in the compiler environment of your choice. You can either build Google Test as a standalone project or it can be incorporated into an existing CMake build for another project.
Standalone CMake Project
When building Google Test as a standalone project, the typical workflow starts with:
mkdir mybuild # Create a directory to hold the build output.
cd mybuild
cmake ${GTEST_DIR} # Generate native build scripts.
If you want to build Google Test’s samples, you should replace the last command with
cmake -Dgtest_build_samples=ON ${GTEST_DIR}
If you are on a *nix system, you should now see a Makefile in the current directory. Just type ‘make’ to build gtest.
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
Studio.
On Mac OS X with Xcode installed, a .xcodeproj
file will be generated.
Incorporating Into An Existing CMake Project
If you want to use gtest in a project which already uses CMake, then a more
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
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 GoogleTest’s source code available to the
main build can be done a few different ways:
- Download the GoogleTest source code manually and place it at a known location. This is the least flexible approach and can make it more difficult to use with continuous integration systems, etc.
- Embed the GoogleTest source code as a direct copy in the main project’s source tree. This is often the simplest approach, but is also the hardest to keep up to date. Some organizations may not permit this method.
- Add GoogleTest as a git submodule or equivalent. This may not always be possible or appropriate. Git submodules, for example, have their own set of advantages and drawbacks.
- Use CMake to download GoogleTest as part of the build’s configure step. This is just a little more complex, but doesn’t have the limitations of the other methods.
The last of the above methods is implemented with a small piece of CMake code in
a separate file (e.g. CMakeLists.txt.in
) which is copied to the build area and
then invoked as a sub-build during the CMake stage. That directory is then
pulled into the main build with add_subdirectory()
. For example:
New file CMakeLists.txt.in
:
cmake_minimum_required(VERSION 2.8.2)
project(googletest-download NONE)
include(ExternalProject)
ExternalProject_Add(googletest
GIT_REPOSITORY https://github.com/google/googletest.git
GIT_TAG master
SOURCE_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-src"
BINARY_DIR "${CMAKE_CURRENT_BINARY_DIR}/googletest-build"
CONFIGURE_COMMAND ""
BUILD_COMMAND ""
INSTALL_COMMAND ""
TEST_COMMAND ""
)
Existing build’s CMakeLists.txt
:
```cmake
Download and unpack googletest at configure time
configure_file(CMakeLists.txt.in googletest-download/CMakeLists.txt) execute_process(COMMAND ${CMAKE_COMMAND} -G “${CMAKE_GENERATOR}” .
File truncated at 100 lines see the full file