如何组织python/Boost Python项目 [英] How to organise python / Boost Python projects

问题描述

我有一个python项目，我想使用Boost :: Python与某些C ++库进行交互.我想知道其他人如何在同一项目中组织他们的python/boost :: python/C ++代码.

I have a python project, to which I would like to interface with some C++ libraries using Boost::Python. I would like to know how others go about organising their python/boost::python/C++ code within the same project.

按照组织，我的意思是在文件/目录结构，构建过程等方面.

By organisation I mean in terms of file/directory structure, build procedures etc.

推荐答案

在下面的内容中，pif表示Python接口.首先，我有一个名为conv_pif.hpp的通用头文件，其中包含Boost头和C ++ Std Library头等.然后，对于每个boost python模块，我都有一个格式为string_pif.cpp的文件(此处与示例模块genocpp相对应)，其中string大致对应于模块的名称.

In what follows, pif denotes Python InterFace. First I've got a generic header file, called conv_pif.hpp, which has Boost headers and C++ Std Library headers and such. Then for each boost python module, I have a file (here corresponding to the example module genocpp) of the form string_pif.cpp, where string corresponds roughly to the name of the module.

****************************************************************************************
geno_pif.cpp
****************************************************************************************
#include "conv_pif.hpp"
#include <boost/python.hpp>
#include "geno.hpp"

void export_cppvec_conv();

void export_geno()
{
  boost::python::def("write_geno_table_affy6_to_file", write_geno_table_affy6_to_file);
}

BOOST_PYTHON_MODULE(genocpp)
{
  export_geno();
  export_cppvec_conv();
}
*****************************************************************************************

函数export_cppvec_conv对应于从C ++向量到python列表的(模板)转换器.我在文件cppvec_conv_pif.cpp中有实际的转换器.特别是，这定义了export_cppvec_conv，它使用模板实例化，因此我可以不用在geno_pif.cpp中包含它而逃脱.为了说明起见，export_cppvec_conv的内容如下，其中cppvec_to_python_list和cppvec_from_python_list在cppvec_conv_pif.cpp的正文中定义.

The function export_cppvec_conv corresponds to a (templated) converter to/from C++ vectors to python lists. I have the actual converters in the file cppvec_conv_pif.cpp. In particular, this defines export_cppvec_conv, which uses template instantatiation, so I can get away without including it in geno_pif.cpp. For illustration, the contents of export_cppvec_conv are as follows, where cppvec_to_python_list and cppvec_from_python_list are defined in the body of cppvec_conv_pif.cpp.

******************************************
cppvec_conv_pif.cpp (extract)
******************************************
void export_cppvec_conv()
{
  boost::python::to_python_converter<vector<double>, cppvec_to_python_list<double> >();
  cppvec_from_python_list<double>();

  boost::python::to_python_converter<vector<int>, cppvec_to_python_list<int> >();
  cppvec_from_python_list<int>();

  boost::python::to_python_converter<vector<string>, cppvec_to_python_list<string> >();
  cppvec_from_python_list<string>();
}
******************************************

一个人可以添加genocpp模块所需的尽可能多的转换器. 然后，当然，我在geno.hpp中有了geno函数的头文件. 最后，我有一个Scons文件，它将所有内容链接在一起

One can add as many converters as needed for the genocpp module. Then of course I've got the headers for the geno functions in geno.hpp. Finally, I have a Scons file which links everything together

******************************************
Sconstruct
******************************************
#!/usr/bin/python

import commands, glob, os

# Common file, for both executables and Python Interface
common_files = """geno print"""

def pyversion():
    pystr = commands.getoutput('python -V')
    version = pystr.split(' ')[1]
    major, minor = version.split('.')[:2]
    return major + '.' + minor

common_base = Split(common_files)
common = [f + ".cpp" for f in common_base]

# For Python interface only
pif_conv = Split("cppvec_conv cppmap_conv cppset_conv")
pif_conv_files = [t+"_pif.cpp" for t in pif_conv]

pif = Split("geno")
pif_files = [t+"_pif.cpp" for t in pif]

# Boost Python Environment
boost_python_env = Environment(
    CPPPATH=["/usr/include/python"+pyversion(), "."],
    CXXFLAGS='-ftemplate-depth-100 -fPIC -Wall -Werror -pedantic -pipe -O3 -ffast-math -march=opteron',
    #CXXFLAGS='-ftemplate-depth-100 -fPIC -Wall -pedantic -O0 -g',
    CPPDEFINES=['BOOST_PYTHON_DYNAMIC_LIB'],
    LIBPATH=["/usr/lib/python"+pyversion()+"/config"],
    LIBS=["python"+pyversion(), "m", "boost_python"],
    SHLIBPREFIX="", #gets rid of lib prefix
    SHOBJSUFFIX = ".bpo"
)

boost_python_env.SharedLibrary(target='genocpp', source = common + pif_conv_files + pif_files)

在这种情况下，只有一个模块，因此pif_files仅具有geno_pif.cpp.否则，我将只选择我想要的模块.嗯，也许将一个工作示例上传到某个地方可能是最简单的.如果有人对更多细节感兴趣，我想我可以编辑它吗?

In this case, there is only one module, so pif_files just has geno_pif.cpp. Otherwise, I would select just those I want for the module. Hmm, maybe it would be easiest to just upload a working example somewhere. If anyone is interested in more detail, I guess I could edit this?

问候，法赫姆

这篇关于如何组织python/Boost Python项目的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！