boostorg / boostorg/python

./b2 install --prefix=$VIRTUALENV does not honour `include/pythonX.Ym`

未关闭
#100 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
C++
星标
537
派生
223
平均合并
11 小时 22 分钟
30 天内合并 PR
2

描述

[PEP 3149](https://www.python.org/dev/peps/pep-3149/) introduced optional flags to the Python installation (see also [this](http://stackoverflow.com/questions/16675865/difference-between-python3-and-python3m-executables) SO question), that are propagated to the virtualenv.

Specifically, the virtualenv include dir is built as `.virtualenvs/.../include/python3.6m` instead of `.virtualenvs/.../include/python3.6` when certain conditions are met. However, running

```
./bootstrap.sh --prefix=$VIRTUAL_ENV --with-libraries=python --with-python=$VIRTUAL_ENV/bin/python
./b2 install --prefix=$VIRTUAL_ENV
```

will call the compiler as
```g++ ... -I".../include/python3.6" ... "libs/python/src/object_operators.cpp"```, causing Python headers to not be found.

IMO Boost.python should honor the default installation within a virtualenv.

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。