On 8/3/2014 12:12 PM, Jürgen Hunold wrote:
Hi Edward,
Am Samstag, 2. August 2014, 20:28:42 schrieb Edward Diener:
On 8/2/2014 5:31 AM, Jürgen Hunold wrote:
It even needs more caretaking. After fixing boost-build.jam to point to the new build system location, I had to tweak the example itself. Full patch to get things compiling again attached.
Does not this need to go into the upcoming 1.56 release ?
Well, the Boot.Build setup broke due to modularization. The other fault seems to be much older, so this should not be deemed release critical. It should certainly be fixed for 1.56.1 / 1.57.0 though.
Would you prepare a pull request? I doubt that Boost.Python is actively maintained, so this might be an issue for the maintenance team. And it might be wise to add the example to the regression tests...
When I tried the quickstart with your changes it fixes the Boost Build issue previously seen. But another issue occurs, both in the quickstart instructions or when I try to run bjam in the Boost Python build directory:
..\..\..\../boost/python/detail/wrap_python.hpp:50:23: fatal error: pyconfig.h: No such file or directory # include
Do you have any idea where pyconfig.h is supposed to be ?