简体   繁体   English

boost.build与boost.python

[英]boost.build Vs boost.python

Context -- Trying to use Boost.Python set of C++ libraries to interface with C++ code. 上下文-尝试使用Boost.Python C ++库集与C ++代码进行交互。 Main idea is to test C++ code (.so files) by using them like python from a QA point of view. 主要思想是从QA角度通过像python一样使用它们来测试C ++代码(.so文件)。

Questions now; 现在的问题;

  1. BOOST_PYTHON_MODULE wrapper, do we really need to include in every .cpp to be interfaced from Python? BOOST_PYTHON_MODULE包装器,我们真的需要在每个.cpp中包括从Python接口的接口吗? Say we have test.cpp, can't we have Boost wrapper written test_qa.cpp so that actual dev code is not changed in the process? 假设我们有test.cpp,难道我们没有将Boost包装器编写为test_qa.cpp以便实际的开发代码不会在此过程中更改吗?

  2. Looked Boost.org site to get more clarity, what is the difference between Boost.Build and Boost.Python? 看起来Boost.org网站更加清晰,Boost.Build和Boost.Python有什么区别?

From the Boost Build documentation : Boost Build文档中

Boost.Build is an easy way to build C++ projects, everywhere. Boost.Build是在任何地方构建C ++项目的简便方法。

From the Boost Python documentation : Boost Python文档中

... a C++ library which enables seamless interoperability between C++ and the Python programming language ...一个C ++库,可实现C ++和Python编程语言之间的无缝互操作性

I would say the difference between these two parts of Boost should be pretty obvious. 我想说,Boost的这两个部分之间的区别应该很明显。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM