Just wanted to post an update to let others know. I did some more debugging and it turns out that even though my PYTHONPATH and PATH variables were set correctly, Python was still not loading the DLL properly (process manager proved the paths were read, the dll was opened/closed, but it kept throwing conflicts to missing paths that were indeed set and errored out). The paths I used were the build paths generated: lib/python38/site-packages and tools/OpenImageIO/ directories when building via VCPKG. If I built the Cmake with the latest repository I used the bin/ directory instead of tools.
While I’m still trying to track down the exact conflict occurring here with using the default build locations, if I copy the .pyd and have it in the same directory location as the dll, then Python resolves the path and OIIO imports correctly. I've done some standard image tests and so far no conflict or issues with this module imported. I suspect that there is a dll conflict somewhere in my original build locations, but so far haven’t found it. I can place the dlls and pyd into a custom location and it still works properly. It's strange that the default build locations cause a problem, but I want a clean install location anyways so this works in my case. I’m seeing this conflict as a definite issue on my system that may not even be OIIO related so please consider this closed. Again, I hope it can help others if they have a similar issue. -Dave
_______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
