It does ring a bell, but I don't remember the specifics, sorry. Can you
maybe install a local Python2.7 and not use the one vckpg installs? Or
maybe it was something when installing Visual Studio.
---
Simon Björk
Compositor/TD
+46 (0)70-2859503
www.bjorkvisuals.com
Thanks, I changed the entries in the pybind11 portfile as well as in the
OpenImageIO portfile to point to Python 2.7. and it compiles without
complaints.
But importing the final module into python fails (python crashes):
>>> import OpenImageIO as oii
Fatal Python error: PyThreadState_Get: no c
You can build Python2.7 bindings with OIIO. I don't know why they changed
to Python3, but in \vcpkg-master\ports\pybind11\portfile.make you can
replace Python3 with Python2.
---
Simon Björk
Compositor/TD
+46 (0)70-2859503
www.bjorkvisuals.com
Den tis 5 maj 2020 kl 1
Hi,
I tried to compile the current OIIO 2.2.3 myself. The reason why I not
use vcpkg is that I need the python2.7 bindings, with vcpkg I was unable
to build a working 2.7 python library.
So I decieded to try it myself. I use cmake-gui and try to build a
static version of the OIIO libs. My pl