#3544 closed Feature Requests (fixed)
Please add --pythonid to the build system
| Reported by: | Owned by: | Vladimir Prus | |
|---|---|---|---|
| Milestone: | Boost 1.42.0 | Component: | Building Boost |
| Version: | Boost 1.40.0 | Severity: | Problem |
| Keywords: | Cc: | til@…, smr@… |
Description
To build the boost python binding and the boost mpi python bindings for different Python versions (eg. for Debian packages), different versions of the Python bindings must be compiled.
With current --buildid option the id is added to all libraries. This works fine for the Python buildings, because they do not depend on other boost libraries. But for the Python mpi bindings it's not optimal, because they then depend on versions of libboost-mpi and libboost-serialization with the buildid.
The --pythonid option which is intoduced by the attached pach only adds the id to libboost-python and libboost-mpi-python.
The current patch does not add the id to the Python module (mpi.so). This is because I could not figure out how to add an id to the module name. However it would probably be nice to add it there as well.
Attachments (1)
Change History (8)
by , 13 years ago
| Attachment: | boost_build_pythonid.patch added |
|---|
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Yes exactly. I want to build the python bindings for all versions of python in Debian, but I don't want to build N versions of boost_serialization and boost_mpi.
comment:3 by , 13 years ago
| Milestone: | Boost 1.41.0 → Boost 1.42.0 |
|---|---|
| Owner: | set to |
| Status: | new → assigned |
comment:4 by , 13 years ago
| Cc: | added |
|---|
FYI, it appears that Boost 1.41 treats "--python" prefixed options (e.g. --pythonid) special and broke this patch; c.f. https://svn.boost.org/trac/boost/ticket/3814
Easy workaround: use --xpythonid instead.
comment:5 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:6 by , 13 years ago
Thank you for the patch, I've checked it it. I've changed the option from --python-id to --python-buildid to better reflect that it's parallel to --buildid option. I've also mentioned it in the --help output.
Thanks, Volodya
comment:7 by , 12 years ago
Volodya: in 1.44, it seems that the libs/mpi part of the patch is not present. Can you check what happened? Maybe missing a merge from "trunk" to "release"?
Thanks, -Steve
Just to clarify, is the problem with --buildid that you want N versions of python libraries, but you don't want N versions of boost_serialization that python/mpi bindings depend on?