gtest

C++ project with Bazel and GTest

匿名 (未验证) 提交于 2019-12-03 01:33:01
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I want to create a Bazel C++ project with gtest for unit tests. What is the minimal setup? (I only have Bazel installed on my computer and I am running under Linux) 回答1: The project structure is: Files related to Bazel+GTest WORKSPACE There you download gtest from github: new_git_repository( name = "googletest", build_file = "gmock.BUILD", remote = "https://github.com/google/googletest", tag = "release-1.8.0", ) You define a gmock BUILD file defined below: gmock.BUILD This BUILD file is in charge of compiling gtest/gmock: cc_library( name =

googletest Undefined symbols for architecture x86_64 error

匿名 (未验证) 提交于 2019-12-03 01:25:01
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: Let GTEST_DIR be the environment variable storing the path to the googletest directory. (I cloned googletest-master from googletest's github repo .) I cd 'ed into $GTEST_DIR , did a mkdir build && cd build , then executed the following command : cmake .. -DCMAKE_C_COMPILER=$GNU-6.0.0/bin/gcc-6.0.0 -DCMAKE_CXX_COMPILER=$GNU-6.0.0/bin/g++-6.0.0 where GNU-6.0.0 is the path to my gnu install. This generated a Makefile inside $GTEST_DIR/build that I tweaked as follows : I've added CC = $GNU-6.0.0/bin/gcc-6.0.0 CXX = $GNU-6.0.0/bin/g++-6.0.0 at

Building assimp 3.2 does not work anymore

匿名 (未验证) 提交于 2019-12-03 01:00:01
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试): 问题: I can't build assimp 3.2 anymore. Yesterday it worked but today it doesn't. I am downloading assimp from here . Then I'm doing cmake CMakeLists.txt -G 'Unix Makefiles' and make as described in their INSTALL file. However when doing make I get the following error: [ 84%] Performing configure step for 'gtest' CMake Error at /home/gartenriese/Documents/assimp/assimp-3.2/test/gtest/src/gtest-stamp/gtest-configure.cmake:16 (message): Command failed: 1 '/usr/bin/cmake' '-DCMAKE_BUILD_TYPE=' '-Dgtest_force_shared_crt=ON' '-Dgtest_disable_pthreads

Cmakelists配置多级目录的gtest项目(项目代码和测试代码分离)

孤者浪人 提交于 2019-11-28 09:59:20
cmake一些语法定义 之前的博客主要写了怎么配置gtest项目,但是一般项目代码和测试代码并不在一起,所以尝试将代码分离 主要分成三个部分,下面给出demo的分级目录 --gtest_demo --CMakelists.txt --src --------cacl.h --------cacl.cpp --------string_util.h --------string_util.cpp --------CMakelists.txt --gtest --------test_calc.cpp --------test_string_util.cpp --------CMakelists.txt 首先先配置根目录下的cmake文件 gtest_demo/CMakelists.txt # 工程名 set (PROJECT_NAME my-gtest) PROJECT(${PROJECT_NAME}) message("工程名: " ${PROJECT_NAME}) message("工程目录: " ${PROJECT_SOURCE_DIR}) # 最低版本需求 cmake_minimum_required(VERSION 3.6) SET(CMAKE_BUILD_TYPE "DEBUG") set (EXECUTABLE_OUTPUT_PATH ${PROJECT_BINARY

Google开源C++单元测试框架Google Test【转】

岁酱吖の 提交于 2019-11-26 18:32:36
gtest是个好test... 原文:http://www.cnblogs.com/coderzh/archive/2009/04/06/1426755.html 前段时间学习和了解了下Google的开源C++单元测试框架Google Test,简称gtest,非常的不错。 我们原来使用的是自己实现的一套单元测试框架,在使用过程中,发现越来越多使用不便之处,而这样不便之处,gtest恰恰很好的解决了。 其实gtest本身的实现并不复杂,我们完全可以模仿gtest,不断的完善我们的测试框架, 但最后我们还是决定使用gtest取代掉原来的自己的测试框架,原因是: 1.不断完善我们的测试框架之后就会发觉相当于把gtest重新做了一遍,虽然轮子造的很爽,但是不是必要的。 2.使用gtest可以免去维护测试框架的麻烦,让我们有更多精力投入到案例设计上。 3.gtest提高了非常完善的功能,并且简单易用,极大的提高了编写测试案例的效率。 gtest的官方网站是: http://code.google.com/p/googletest/ 从官方的使用文档里,你几乎可以获得你想要的所有东西 http://code.google.com/p/googletest/wiki/GoogleTestPrimer http://code.google.com/p/googletest/wiki