blocks|key|5677220|text|在对交叉编译的代码进行单元测试时，我的做法是使用本机工具链编译单元测试本身--通常是某种风格的x86编译器。这些单元测试在构建机器上执行，而不是在嵌入式目标上执行。如果您正在使用存根和模拟编写严格的单元测试(而不是集成测试)，则不应该依赖于嵌入式硬件。如果不是..。开始永远不会太晚。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5677221|这种方法的一个额外好处是，对于非x86嵌入式目标，这种类型的单元测试有助于清除字节顺序问题、未初始化的变量和其他有趣的bug。|5677222|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

My practice when unit testing code that is cross compiled is to compile the unit tests themselves using the native toolchain -- usually some flavor of x86 compiler. These unit tests execute on the build machine rather than on the embedded target. If you're writing strict unit tests (as opposed to integration tests) with stubs and mocks you shouldn't have dependencies on embedded hardware. If not... it's never too late to start.

One added benefit of this approach is that for non-x86 embedded targets, this type of unit testing helps flush out endianness issues, uninitialized variables and other interesting bugs.

blocks|key|490236|text|./configure+--prefix=/sandBox+--build=`config.guess`+--host=sh4-linux|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|490237|sh4-linux是您想要运行程序的平台。|unstyled|490238|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>./configure --prefix=/sandBox --build=`config.guess` --host=sh4-linux
</code></pre>

sh4-linux is the platform where you want to run the program.

blocks|key|3565343|text|你可能想看看CxxTest。我没有将它用于交叉编译，但它完全基于头文件和Python脚本-没有编译库。它可能比其他的更容易适应。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3565344|entityMap|0|LINK|mutability|MUTABLE|url|http://cxxtest.com/^0|6|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You might want to look at <a href="http://cxxtest.com" rel="nofollow noreferrer">CxxTest</a>. I have not used it for cross compilation, but it is based entirely on headers and a Python script - no compiled library. It might be easier to adapt than others.

blocks|key|2401767|text|我在这里不提供答案，但我不会接受不在不同目标上运行单元测试的建议:您仍然需要在不同的目标上运行单元测试，最好是系统测试和单元测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2401768|否则，像ARM/其他嵌入式CPU上的对齐错误这样简单的事情就不会被捕获。|2401769|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Im not providing an answer here, but i wouldn't take the advice of NOT running your unit tests on different targets : you still need to, preferably both system and unit tests.

Otherwise simple things like alignment errors on ARM/other embedded CPUs will not get caught.

blocks|key|3565599|text|要交叉编译CppUTest+(v3.3)，我必须覆盖LD、CXX和CC+make变量。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3565600|为了获得构建的CppUTest和CppUTestExt+(针对CppUMock)库及其测试，我使用了CPPUTEST_HOME目录中的以下命令：|3565601|构建libCppUTest.a：|3565602|make+all+LD=sh4-linux-g%2B%2B+CXX=sh4-linux-g%2B%2B+CC=sh4-linux-gcc|code-block|syntax|javascript|3565603|构建libCppUTestExt.a+(用于CppUMock)：|3565604|make+extensions+LD=sh4-linux-g%2B%2B+CXX=sh4-linux-g%2B%2B+CC=sh4-linux-gcc|3565605|然后，您可以将CPPUTEST_HOME中生成的CppUTest_tests和CppUTestExt_tests可执行文件复制到目标设备，并在那里执行它们。|3565606|假设CppUTest在您的目标上通过了它自己的测试，那么您就可以使用CppUTest开发您的测试了。只需将测试代码与交叉编译的CppUTest库链接起来，并将生成的可执行文件复制到您的目标。然后运行以从目标平台本身获取单元测试结果。|3565607|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|Z|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

To cross-compile CppUTest (v3.3), I had to override the LD, CXX and CC make variables.

To get both the CppUTest and CppUTestExt (for CppUMock) libraries and their tests built I used the following commands from the CPPUTEST_HOME directory:

To build libCppUTest.a:

<pre><code>make all LD=sh4-linux-g++ CXX=sh4-linux-g++ CC=sh4-linux-gcc
</code></pre>

To build libCppUTestExt.a (for CppUMock):

<pre><code>make extensions LD=sh4-linux-g++ CXX=sh4-linux-g++ CC=sh4-linux-gcc
</code></pre>

You can then copy the CppUTest_tests and CppUTestExt_tests executables that are produced in your CPPUTEST_HOME to your target device and execute them there.

Assuming CppUTest passes it's own tests on your target, you're then ready to develop your tests with CppUTest. Just link your test code with the cross-compiled CppUTest libraries and copy the resulting executable to your target. Then run to get unit test results from the target platform itself.

blocks|key|2397040|text|听起来您需要为您的操作系统和架构以及您的开发/构建机器上的内容编译单元测试库。为此，我更喜欢使用Boost%2B%2B单元测试框架。CppUnit可能更容易交叉编译，还没试过。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2397041|我对新目标的设置是为我的目标OS/arch编译必要的Boost%2B%2B库，然后编写测试以链接到Boost%2B%2B库和要测试的代码。|2397042|这样做的好处是可以链接到您的x86+Linux或目标Boost%2B%2B库，因此您可以在目标和开发/构建机器上运行测试。|2397043|我的一般设置如下所示：|2397044|libs/boost/<arch>/<boost+libs>
src/foo.{cpp,h}
tests/test_foo.cpp
build/foo
build/test_foo.<arch>|code-block|syntax|javascript|2397045|我将编译后的Boost%2B%2B库放在我所有项目所需的libs/+dir目录下，并在我的Makefiles中引用这些库。源代码和测试是使用指定的arch变量构建的，这样我就可以在我的开发机器上运行test_foo.x86，在我的目标上运行test_foo.{arm，mips，ppc，等等)。|2397046|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|U|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

It sounds like you need to have unit test library compiled for your OS and architecture as well as what's on your dev/build machine(s). I prefer Boost++ unit test framework for this. You can either download something that's prebuilt for your architecture, but will usually have to compile it yourself. I found a few solutions by googling for how to cross-compile boost (e.g. <a href="http://goodliffe.blogspot.com/2008/05/cross-compiling-boost.html" rel="nofollow">http://goodliffe.blogspot.com/2008/05/cross-compiling-boost.html</a>). CppUnit might be easier to cross-compile, haven't tried. The general principle is the same, you compile the same library version for your development architecture and for your target machine

My setup for new targets is to compile the necessary Boost++ libraries for my target OS/arch and then write tests to link against both Boost++ libraries and the code to be tested.

The benefit is that you can link against your x86 Linux Boost++ libs or against your target Boost++ libs, thus you can run the tests on both your target and your dev/build machine(s).

My general setup looks like this:

<pre><code>libs/boost/&lt;arch&gt;/&lt;boost libs&gt;
src/foo.{cpp,h}
tests/test_foo.cpp
build/foo
build/test_foo.&lt;arch&gt;
</code></pre>

I put compiled Boost++ libs under different architectures that I need in libs/ dir for all my projects and reference those libs in my Makefiles. The source and the tests get build with an arch variable specified to make command that way I can run test_foo.x86 on my dev machine and test_foo.{arm,mips,ppc,etc.} on my targets.

Has anyone used a package like CppUnit to cross-compile C++ unit tests to run on an embedded platform?

I'm using G++ on a Linux box to compile executables that must be run on a LynxOS board. I can't seem to get any of the common unit test packages to configure and build something that will create unit tests.

I see a lot of unit test packages, CppUnit, UnitTest++, GTest, CppUTest, etc., but very little about using these packages in a cross-compiler scenario. The ones with a "configure" script imply that this is possible, but I can't seem to get them to configure and build.

Cross compiling unit tests with CppUnit or similar

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

有没有人使用过像CppUnit这样的包来交叉编译C++单元测试，以便在嵌入式平台上运行？我在Linux机器上使用G++来编译必须在LynxOS板上运行的可执行文件。我似乎无法获得任何常见的单元测试包来配置和构建将创建单元测试的东西。我看到了很多单元测试包，如CppUnit、UnitTest++、GTest、CppUTest等，但在交叉编译器场景中使用这些包的情况却很少。那些带有" configur

问使用CppUnit或类似工具交叉编译单元测试
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用CppUnit或类似工具交叉编译单元测试EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用CppUnit或类似工具交叉编译单元测试
EN