### 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](https://github.com/google/googletest/blob/master/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
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}" .
RESULT_VARIABLE result
WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/googletest-download )
if(result)
message(FATAL_ERROR "CMake step for googletest failed: ${result}")
endif()
execute_process(COMMAND ${CMAKE_COMMAND} --build .
RESULT_VARIABLE result
WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/googletest-download )
if(result)
message(FATAL_ERROR "Build step for googletest failed: ${result}")
endif()
# Prevent overriding the parent project's compiler/linker
# settings on Windows
set(gtest_force_shared_crt ON CACHE BOOL "" FORCE)
# Add googletest directly to our build. This defines
# the gtest and gtest_main targets.
add_subdirectory(${CMAKE_CURRENT_BINARY_DIR}/googletest-src
${CMAKE_CURRENT_BINARY_DIR}/googletest-build
EXCLUDE_FROM_ALL)
# The gtest/gtest_main targets carry header search path
# dependencies automatically when using CMake 2.8.11 or
# later. Otherwise we have to add them here ourselves.
if (CMAKE_VERSION VERSION_LESS 2.8.11)
include_directories("${gtest_SOURCE_DIR}/include")
endif()
# Now simply link against gtest or gtest_main as needed. Eg
add_executable(example example.cpp)
target_link_libraries(example gtest_main)
add_test(NAME example_test COMMAND example)
```
Note that this approach requires CMake 2.8.2 or later due to its use of the
`ExternalProject_Add()` command. The above technique is discussed in more detail
in [this separate article](http://crascit.com/2015/07/25/cmake-gtest/) which
also contains a link to a fully generalized implementation of the technique.
##### Visual Studio Dynamic vs Static Runtimes
By default, new Visual Studio projects link the C runtimes dynamically but
Google Test links them statically. This will generate an error that looks
something like the following: gtest.lib(gtest-all.obj) : error LNK2038: mismatch
detected for 'RuntimeLibrary': value 'MTd_StaticDebug' doesn't match value
'MDd_DynamicDebug' in main.obj
Google Test already has a CMake option for this: `gtest_force_shared_crt`
Enabling this option will make gtest link the runtimes dynamically too, and
match the project in which it is included.
#### C++ Standard Version
An environment that supports C++11 is required in order to successfully build
Google Test. One way to ensure this is to specify the standard in the top-level
project, for example by using the `set(CMAKE_CXX_STANDARD 11)` command. If this
is not feasible, for example in a C project using Google Test for validation,
then it can be specified by adding it to the options for cmake via the
`DCMAKE_CXX_FLAGS` option.
### Tweaking Google Test
Google Test can be used in diverse environments. The default configuration may
not work (or may not work well) out of the box in some environments. However,
you can easily tweak Google Test by defining control macros on the compiler
command line. Generally, these macros are named like `GTEST_XYZ` and you define
them to either 1 or 0 to enable or disable a certain feature.
We list the most frequently used macros below. For a complete list, see file
[include/gtest/internal/gtest-port.h](https://github.com/google/googletest/blob/master/googletest/include/gtest/internal/gtest-port.h).
### Multi-threaded Tests
Google Test is thread-safe where the pthread library is available. After
`#include "gtest/gtest.h"`, you can check the
`GTEST_IS_THREADSAFE` macro to see whether this is the case (yes if the macro is
`#defined` to 1, no if it's undefined.).
If Google Test doesn't correctly detect whether pthread is available in your
environment, you can force it with
-DGTEST_HAS_PTHREAD=1
or
-DGTEST_HAS_PTHREAD=0
When Google Test uses pthread, you may need to add flags to your compiler and/or
linker to select the pthread library, or you'll get link errors. If you use the
CMake script, this is taken care of for you. If you use your own
没有合适的资源?快使用搜索试试~ 我知道了~
扩展卡尔曼滤波器,平方根扩展卡尔曼滤波器(SR-EKF),无迹卡尔曼滤波器(UKF),平方根无迹卡尔曼滤波器(SR-UKF
共309个文件
cc:102个
py:49个
h:48个
需积分: 0 4 下载量 128 浏览量
2023-10-28
09:54:54
上传
评论
收藏 1.21MB ZIP 举报
温馨提示
扩展卡尔曼滤波器,平方根扩展卡尔曼滤波器(SR-EKF),无迹卡尔曼滤波器(UKF),平方根无迹卡尔曼滤波器(SR-UKF
资源推荐
资源详情
资源评论
收起资源包目录
扩展卡尔曼滤波器,平方根扩展卡尔曼滤波器(SR-EKF),无迹卡尔曼滤波器(UKF),平方根无迹卡尔曼滤波器(SR-UKF (309个子文件)
BUILD.bazel 14KB
BUILD.bazel 5KB
BUILD.bazel 3KB
gmock-matchers_test.cc 269KB
gtest_unittest.cc 247KB
gtest.cc 237KB
gtest_pred_impl_unittest.cc 76KB
gmock-spec-builders_test.cc 73KB
gtest-death-test.cc 61KB
googletest-printers-test.cc 55KB
gmock-actions_test.cc 50KB
googletest-death-test-test.cc 47KB
gtest-port.cc 46KB
googletest-param-test-test.cc 40KB
googletest-port-test.cc 39KB
googletest-output-test_.cc 35KB
gmock-generated-actions_test.cc 34KB
gmock-spec-builders.cc 33KB
gmock-function-mocker_test.cc 30KB
gmock-internal-utils_test.cc 26KB
gmock-more-actions_test.cc 24KB
googletest-listener-test.cc 24KB
googletest-filepath-test.cc 22KB
gmock-matchers.cc 18KB
gtest-typed-test_test.cc 15KB
gtest-printers.cc 14KB
gmock-nice-strict_test.cc 14KB
gtest-filepath.cc 14KB
gtest-unittest-api_test.cc 13KB
gmock-cardinalities_test.cc 12KB
gtest_stress_test.cc 9KB
sample6_unittest.cc 9KB
gmock-pp-string_test.cc 9KB
gmock_output_test_.cc 8KB
googletest-catch-exceptions-test_.cc 8KB
gmock.cc 8KB
googletest-test-part-test.cc 8KB
googletest-options-test.cc 8KB
gmock-internal-utils.cc 7KB
gtest_repeat_test.cc 7KB
gmock_stress_test.cc 7KB
sample5_unittest.cc 6KB
gtest_environment_test.cc 6KB
gmock_test.cc 6KB
gtest_xml_output_unittest_.cc 6KB
sample8_unittest.cc 6KB
sample9_unittest.cc 6KB
googletest-failfast-unittest_.cc 5KB
sample3_unittest.cc 5KB
googletest-message-test.cc 5KB
gmock-cardinalities.cc 5KB
sample1_unittest.cc 5KB
sample10_unittest.cc 5KB
googletest-list-tests-unittest_.cc 5KB
sample7_unittest.cc 5KB
gtest_premature_exit_test.cc 4KB
gtest-test-part.cc 4KB
sample2_unittest.cc 4KB
gtest-typed-test.cc 4KB
gtest_assert_by_exception_test.cc 4KB
gtest_test_macro_stack_footprint_test.cc 4KB
gtest-matchers.cc 4KB
googletest-env-var-test_.cc 4KB
googletest-death-test_ex_test.cc 4KB
gmock-pp_test.cc 3KB
googletest-filter-unittest_.cc 3KB
gtest_throw_on_failure_ex_test.cc 3KB
gmock_ex_test.cc 3KB
gtest_list_output_unittest_.cc 3KB
googletest-break-on-failure-unittest_.cc 3KB
gmock_leak_test_.cc 3KB
googletest-shuffle-test_.cc 3KB
googletest-throw-on-failure-test_.cc 3KB
gmock_main.cc 3KB
googletest-param-test2-test.cc 3KB
googletest-color-test_.cc 2KB
sample1.cc 2KB
gtest_no_test_unittest.cc 2KB
gmock_all_test.cc 2KB
sample2.cc 2KB
gtest_all_test.cc 2KB
gtest_sole_header_test.cc 2KB
gtest-all.cc 2KB
gtest_prod_test.cc 2KB
googletest-param-test-invalid-name2-test_.cc 2KB
sample4.cc 2KB
gmock-all.cc 2KB
gtest_help_test_.cc 2KB
gtest_skip_in_environment_setup_test.cc 2KB
googletest-param-test-invalid-name1-test_.cc 2KB
gtest-typed-test2_test.cc 2KB
gtest_skip_test.cc 2KB
sample4_unittest.cc 2KB
gmock-port_test.cc 2KB
gtest_main.cc 2KB
gtest_xml_outfile1_test_.cc 2KB
gtest_xml_outfile2_test_.cc 2KB
googletest-setuptestsuite-test_.cc 2KB
gtest_testbridge_test_.cc 2KB
googletest-uninitialized-test_.cc 2KB
共 309 条
- 1
- 2
- 3
- 4
资源评论
Older司机渣渣威
- 粉丝: 5
- 资源: 202
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- Flume进阶-自定义拦截器jar包
- Dubins曲线算法讲解和在运动规划中的使用.pdf
- 上市公司-股票性质数据-工具变量(民企、国企、央企)2003-2022年.dta
- 上市公司-股票性质数据-工具变量(民企、国企、央企)2003-2022年.xlsx
- Reeds+Shepp曲线算法讲解和实现.pdf
- 毕业设计基于SpringBoot+MyBatisPlus+MySQL+Vue的外卖配送信息系统源代码+数据库
- 词向量(Word Embeddings)是自然语言处理(NLP)领域的一种重要技术.txt
- Surfer,线性函数
- MyBatis 的动态 SQL 是其核心特性之一.txt
- 时代的sdddsddsddsd
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功