【问题标题】:Cant compile googletest on OSX Yosemite无法在 OSX Yosemite 上编译 googletest
【发布时间】:2021-10-11 14:29:50
【问题描述】:

我已经阅读了一些相关的答案和一些在线文章以及官方的谷歌测试文档,但由于我缺乏这方面的经验,所以我对一些事情非常不安全并寻求指导。

我正在用 C++ 开始一个全新的宠物项目,我想在编写代码的同时编写适当的测试,遇到 Google Test 并决定试一试。

目前这是我的文件夹结构:

/
/bin
/main.cpp
/lib
/lib/db
/lib/external/googletest

我的想法是将测试和类文件放在自己的文件夹中,例如:

/lib/db/db.h
/lib/db/db.cpp
/lib/db/db.test

问题 #1

包含测试的文件是否有命名约定或期望? (上面那个例子中的/lib/db/db.test

问题 #2

我运行了以下命令

  1. cd lib/external/googletest/googletest
  2. cmake .
  3. 制作
  4. 进行安装
  5. cp lib*.a /usr/local/lib
  6. cp -r 包含/gtest/ /usr/local/include/

看到它最终如何在 /usr/local/include/gtest 中创建一系列 .h 文件,我希望能够#include <gtest/gtest.h> 并能够运行测试,我将其添加到我的 main.cpp :

TEST(Param1, Param2) {
    EXPECT_EQ(1, 1);
}

在构建时出现以下错误:

Undefined symbols for architecture x86_64:
  "testing::AssertionSuccess()", referenced from:
      testing::AssertionResult testing::internal::CmpHelperEQ<int, int>(char const*, char const*, int const&, int const&) in main-230b96.o
  "testing::Test::SetUp()", referenced from:
      vtable for Param1_Param2_Test in main-230b96.o
  "testing::Test::TearDown()", referenced from:
      vtable for Param1_Param2_Test in main-230b96.o
  "testing::Test::Test()", referenced from:
      Param1_Param2_Test::Param1_Param2_Test() in main-230b96.o
  "testing::Test::~Test()", referenced from:
      Param1_Param2_Test::~Param1_Param2_Test() in main-230b96.o
  "testing::Message::Message()", referenced from:
      Param1_Param2_Test::TestBody() in main-230b96.o
  "testing::internal::AssertHelper::AssertHelper(testing::TestPartResult::Type, char const*, int, char const*)", referenced from:
      Param1_Param2_Test::TestBody() in main-230b96.o
  "testing::internal::AssertHelper::~AssertHelper()", referenced from:
      Param1_Param2_Test::TestBody() in main-230b96.o
  "testing::internal::GetTestTypeId()", referenced from:
      ___cxx_global_var_init in main-230b96.o
  "testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)", referenced from:
      ___cxx_global_var_init in main-230b96.o
  "testing::internal::IsTrue(bool)", referenced from:
      testing::internal::scoped_ptr<std::__1::basic_stringstream<char, std::__1::char_traits<char>, std::__1::allocator<char> > >::reset(std::__1::basic_stringstream<char, std::__1::char_traits<char>, std::__1::allocator<char> >*) in main-230b96.o
      testing::internal::scoped_ptr<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >::reset(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >*) in main-230b96.o
  "testing::internal::EqFailure(char const*, char const*, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, bool)", referenced from:
      testing::AssertionResult testing::internal::CmpHelperEQFailure<int, int>(char const*, char const*, int const&, int const&) in main-230b96.o
  "testing::internal::AssertHelper::operator=(testing::Message const&) const", referenced from:
      Param1_Param2_Test::TestBody() in main-230b96.o
  "typeinfo for testing::Test", referenced from:
      typeinfo for Param1_Param2_Test in main-230b96.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [all] Error 1

解决方案

感谢 trojanfoe,我将 makefile 修复为如下所示:

CC=g++
target_folder=bin
all:
    $(CC) *.cpp -o $(target_folder)/prod
    ./bin/prod
test:
    $(CC) *.cpp -o $(target_folder)/test lib/external/googletest/googletest/libgtest.a lib/external/googletest/googletest/libgtest_main.a
    ./bin/test
clean:
    rm -f $(target_folder)/* *.o

现在它工作得很好,请记住这是一个骨架项目,我需要构建测试文件和入口点,所以此时它只是编译一个基本测试。

【问题讨论】:

  • 没有需要链接的库吗?你似乎没有这样做......
  • @trojanfoe 就是这样!我将/usr/local/lib/libgtest_main.a 作为另一个参数添加到makefile 并修复了它!如果您将评论改写为答案,我会将其标记为正确

标签: c++ macos googletest


【解决方案1】:

您忘记将 google 测试库与您的可执行文件链接。

【讨论】:

    猜你喜欢
    • 1970-01-01
    • 2015-07-12
    • 2022-01-20
    • 2014-12-19
    • 1970-01-01
    • 2016-01-14
    • 2015-05-12
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多