Matthias Troyer wrote:
On Jan 25, 2011, at 12:53 PM, Vladimir Prus wrote:
At present, when both mpi and python are configured/detected, Boost.MPI tries to build a python extension which is named, on Linux, mpi.so. When building with --build-type=complete, an attempt to build that file with several properties is made, which Boost.Build detects and complains about.
This was the case for several releases, and nobody seemed to care, but it's still not good. So, could Boost.MPI maintainers express their preference for either:
- Building one variant of mpi.so, no matter what, in which case what variable (debug/release, single/multi threaded)? - Building several, differently named or installed in different places, variants of mpi.so
I would suggest several versions, with the same name but installed in different places. This will allow multiple builds (especially debug / release), without requiring all import statements in the Python codes to be changed to switch version.
Hi Matthias, Could you specify those places, relatively to --prefix? Note that it does not seem like any other package does that, so we don't have prior practice to decide on locations. Thanks, -- Vladimir Prus Mentor Graphics +7 (812) 677-68-40