./b2 install --prefix=$VIRTUALENV does not honour `include/pythonX.Ym`
- 主要言語
- C++
- スター
- 537
- フォーク
- 223
- 平均マージ
- 11時間 22分
- マージ済み PR(30日)
- 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 はまだ評価されていません。