Ok this seems to be a crash in debug mode when I am picking up the
release version of boost_python.dll in my path.
How to make boost build v1 install boost_python.dll next to my
extension? Or do I need to manually copy the correct (debug/release)
version every time I want to debug or run the release version?
I've tried adding
to my stage target to no avail.
I have followed the 'Creating Packages' guidelines in the 'General
Techniques' documentation but could not find any documentation on how to
set up a build environment where I can alternate between debug and
release builds easily.
John Reid wrote:
> John Reid wrote:
>>Joel de Guzman wrote:
>>>That's odd. I can't reproduce your results. To be sure, I added
>>>your test in libs/python/test/vector_indexing_suite.cpp/py.
>>>I'm getting no crash. Please check out the test suite and run it.
> I've investigated further. I wasn't aware of the correct way to run the
> python tests. Now I've recompiled a clean version of boost cvs_head
> everything works ok if I run the tests using 'bjam -sPYTHON_TEST_ARGS=
> test' in the 'boost\libs\python\test' directory.
> What might be relevant is that if I run 'bjam' with no arguments, I can
> generate 'vector_indexing_suite_ext.pyd' in the
> directory. When I manually set PYTHONPATH to this directory and run
> 'python vector_indexing_suite.py' I get the crash as before. Is this
> expected, relevant and/or interesting? I would have thought this would
> just have run that particular test.
> Any help appreciated as always. Thanks,
C++-sig mailing list