Hi Adam,

I recently had to build OIIO for Python 3 on Windows 64 this summer and
have posted my known issues here:
https://www.mail-archive.com/[email protected]/msg05187.html.
You are correct in that PYTHONPATH must include the path to the .pyd file
that allows Python to recognize OIIO. I’m still trying to determine the
conflict of using the default location this file is generated into on my
machine, but as I note in the message link above, I was able to make a copy
of the file to the same directory as the DLL and this worked correctly in
my custom instance of Python being run.

Hope that helps out,

Dave

On Mon, Sep 28, 2020 at 8:47 PM Adam baker <[email protected]> wrote:

> OS: Windows 10
> Python: 3.8 | 2.7
>
> I (believe) have successfully built and installed OpenImageIO through
> vcpkg. Now I am trying to set up the python binding I have read over some
> of the other issues talking about how pybind11 needs to also be installed.
>
> Installed items
> ```openimageio[core,pybind11,tools]:x64-windows```
>
> This is my first attempt trying to build anything of this nature and I am
> not sure what the next steps are.
>
> Repo Steps:
> * git clone vcpkg
> * .\vcpkg\bootstrap-vcpkg.bat
> * openimageio:x64-windows
> * openimageio[pybind11]:x64-windows
> * .\vcpkg integrate install
>
> I am assuming I will have to point a PYTHONPATH but not sure what that
> path would be.  The install.md is not clear on the next step.
>
> Thanks
> - Adam B.
>
> _______________________________________________
> Oiio-dev mailing list
> [email protected]
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
>
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org

Reply via email to