Stefan Seefeld <seefeld@sympatico.ca> writes:
Roland Schwarz wrote:
The g++ in its default configuration creates dll,s that depend on the cygwin1.dll. The used python executable depends on msvc.dll.
I do not understand enough about the python wrapper lib, but my bets are, it will not work loading a plugin that depends on a different runtime dll.
If I am correct, I think the only resolution is to mark this combination as n/a.
The deeper problem: detecting the link compatibility will need more research, and has to be addressed within Boost.Build I guess.
AFAIU, you can compile your own C++ code with 'g++ -mno-cygnus' on
it's -mno-cygwin
cygwin, and are then able to link with a windows-native python runtime.
That's the equivalent of using a mingw toolchain directly.
I'm not sure this is the best time to experiment with toolchains, though, so marking this variant as not available may be the right thing to do.
Boost.Python has always worked with Cygwin GCC, but if you don't use -mno-cygwin, you have to use the cygwin version of Python (the one installed when you select it in the Cygwin installer). Currently the Python support in BBv2 on Windows and Cygwin is a total mess, which may explain why it isn't working for you. I'm trying to fix that up now. -- Dave Abrahams Boost Consulting www.boost-consulting.com