0

I have successfully built boost.python with visual c++ 2010(dynamic library, 64-bit). I have python 2.7.8 64-bit installed on windows 7 64-bit. I've read here that python extensions should be built with the same compiler that was used to build python itself. My question is, since python 2.7.8 was built with visual c++ 2008 64-bit compiler, can I have the following mix?

  1. my python extension built with VC2008 64-bit(to match python itself)
  2. 64-bit boost.python dll built with VC2010 64-bit
  3. python 64-bit, built itself with VC2008 64-bit

I've noticed that boost.python dll depends on python dll and that's why I'm quite worried about the mix.

Improve this question

1 Answer 1

Reset to default
0

I suspect it will work fine. I have seen cases where this sort of thing went wrong (notably, GCC 4.7.0 and 4.7.1 were ABI-incompatible with the releases before and after if you used C++11), but in the case you outlined it has a good chance of working. I'd say give it a try (and report back).

Improve this answer
Sign up to request clarification or add additional context in comments.

2 Comments

I've tried some light scenarios with the mix in the question and so far it's been going good. Also I've seen many other posts(across the web and in other questions here on stack overflow) where people mentioned they built python.boost with visual c++ 2010, so I'm crossing fingers...
I posted the same question here and the answer I received was concerned with multiple c runtime libraries being loaded into the same process(python in this case), and this agrees with my conjecture. It's probably better to stick with building boost.python with visual c++ 2008 64-bit for the moment.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.