I have developed an OpenFX Plugin which uses OpenImageIO for some image
operations.
To get things to build out on Windows I used the USD build club recipes to
build out OpenImageIO.
Whereas on Linux and MacOS everything is statically linked all the way back to
Boost.
Well pretty much, I think Mac uses a dynamic IlmBase.
Is it possible to make everything static on Windows.
The reason I ask is there is no rpath equivalent on Windows so all the shared
libraries are in global scope.
So if I hit half.dll from a different version of IlmBase my Plugins won’t load,
which makes it difficult for end users without debugging skills.
https://kognat.com/forums/topic/windows-shared-libraries/
So are there reproduction steps to build a static OpenImageIO where all it’s
dependencies are static too?
This way I won’t get symbol clashes.
Or is namespacing the way to go?
But I fear the dependencies will also cause issues.
Love to hear any ideas from Windows developers, be gentle my Windows skills are
somewhat limited.
Sam
Sent from my iPhone
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
