Bug #365

Problem with python bindings in boost 1.60

Added by bartus bartus about 2 years ago. Updated over 1 year ago.

Status:NewStart date:07/16/2016
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

When building mitsuba against boost 1.60 there is some additionaly pointers exposition to be done.
Current code produce broken python library, resoulting in following error with blender-mitsuba integrator (whith material preview and render)

No to_python (by-value) converter found for C++ type: mitsuba::ref<mitsuba::TriMesh>

It was misleadingly reported as blender integrator bug.
https://www.mitsuba-renderer.org/tracker/issues/353

I dont find correct solution to address the issue but some googling point me to this answers.
http://stackoverflow.com/questions/5336942/boost-python-call-by-reference-typeerror-no-to-python-by-value-converter-fo
https://mail.python.org/pipermail/cplusplus-sig/2016-January/017362.html

Build environment
  • Linux Arch x86_64
  • boost : 1.60.0-5
  • gcc-5 : 5.4.0
  • mitsuba : git#branch=master, rev=2150:87efb7d6b4b6

PKGBUILD - build script with adjusted for git source and gcc-5 (3.28 KB) bartus bartus, 07/16/2016 10:01 am

py3binding.sh Magnifier - python3 bindings build script with gcc-5 (1.34 KB) bartus bartus, 07/16/2016 10:01 am

History

#1 Updated by bartus bartus about 2 years ago

Also SConscript.configuer and detect_python.py should be update to cover python version up to 3.5 ( this renders py3bindigs.sh obsolete )

#2 Updated by bartus bartus over 1 year ago

[SOLVED] As of boost 1.61 problem no longer appears (mitsuba blender integrator works fine)

Also available in: Atom PDF