简体繁体 English

在VxWorks上构建Apache Thrift

[英]Apache thrift build on VxWorks

原文 2016-02-08 11:59:59 9 1 c++/ thrift/ vxworks

My aim is to use Apache thrift on one of our device having vxWorks 6.8 (C++). 我的目标是在我们的配备vxWorks 6.8（C ++）的设备上使用Apache Thrift。

I need steps to build thrift lib(.so) or sample application on vxWorks. 我需要在vxWorks上构建Thrift lib（.so）或示例应用程序的步骤。 It would be great help if someone could suggest way out. 如果有人可以建议出路，那将是很大的帮助。 I am using Windriver Workbench 3.2 on windows 7 and target is PENTIUM3gnu. 我在Windows 7上使用Windriver Workbench 3.2，目标是PENTIUM3gnu。 I can use boost but not C++ 11. 我可以使用boost但不能使用C ++ 11。

1 个解决方案

Well, as someone who had to make Thrift build on a bog-normal Fedora PC, and as someone who knows the pain of making it work on embedded platforms¹, I can assure you that your confusion is at least partly caused by Thrift's sub-par build system. 好吧，作为必须让Thrift在沼泽普通Fedora PC上构建的人，以及知道使其在嵌入式平台上工作的痛苦¹的人，我可以向您保证，您的困惑至少部分是由Thrift的劣等造成的。构建系统。

I can't actually give you detailed descriptions on how to build it on vxWorks, but here's the general consensus on what needs to be done when building it on something that doesn't happen to be very similar to the maintainer's machines: 我实际上无法为您提供有关如何在vxWorks上进行构建的详细说明，但是这是在与维护者的机器不太相似的基础上进行构建时需要做的一般性共识：

massage all the ./configure options, and explicitly disable every single thing you don't need. 按摩所有./configure选项，并显式禁用不需要的每件事。 Even after much script fixing, I couldn't build the examples/tutorials, so I had to disable them 即使经过大量脚本修复，我也无法构建示例/教程，因此必须禁用它们
explicitly state dependency paths. 明确说明依赖路径。 The autoconfigure scripts seem to have been modified in a manner that makes auto-detection of libraries work worse than it normally does with autoconf 自动配置脚本的修改方式似乎使自动检测库的工作比使用autoconf正常进行的工作差
try to build. 尝试建立。 Find the places where for some reasons, the build system uses hardwired locations and hence fails 查找由于某些原因构建系统使用硬接线位置并因此失败的位置
rinse, repeat. 冲洗，重复。