Boost logo

Boost :

From: rcspython_at_[hidden]
Date: 2001-02-22 12:44:22

Your suggestion was exactly correct. It was a mysterious problem.. I
was was barking up the wrong tree thinking it was an "extern C "

I want to thank you for you excellent response! I was pulling my hair
out over this problem, and falling behind schedule as well.

Best Regards,
--- In boost_at_y..., "David Abrahams" <abrahams_at_m...> wrote:
> Ron,
> I'm not sure exactly what problem you're having, but if you're
making a
> debug build under Win32, you may be running into the following
> Without special treatment, if _DEBUG is defined, #including
> causes you to make a special "python debugging" build of your code,
> needs to be run under a special debugging version of python
> and use special debugging versions of the python DLL. Since most
> don't get those components with a stock Python installation, I
disable the
> special "python debugging" mode in Boost.Python by using
> boost/python/detail/wrap_python.hpp instead of python.h directly
> debugging can be re-enabled with -DDEBUG_PYTHON). You should
probably be
> #including wrap_python.hpp instead of python.h

Boost list run by bdawes at, gregod at, cpdaniel at, john at