Hey
I'm on winodws x64 & got openimageio from vcpkg. v2.3.17.0-ec11bc3a20.clean
I've build it today & tried to link against it but I'm hitting walls.
Here is the "frame" of my app
utility - static library that includes openImageIO shared library. - it
creates then static .lib
mainAppLib = main application library = static .lib
mainAppLib targets utility lib and includes it. Also includes oiio
shared lib/etc.
mainApp = .exe uses mainAppLib as library.
pluginA = .dll uses function from targets utility with openImageIo.
Also includes oiio shared lib/etc.
pluginB = .dll does not use anything from utility class. Also includes
oiio shared lib/etc.
When main app starts, I can see pluginB loading just fine, however
pluginA is throwing >
LoadLibraryW failed - The specified module could not be found
<https://stackoverflow.com/questions/51627705/loadlibrary-failed-the-specified-module-could-not-be-found>
Now if I go to LibraryA and remove include for utility function. PluginA
then loads just fine.
This worked just fine in past in older openimageio versions. I'm not
quite sure which version I used in past of oiio, but I grabbed it about
a year ago or so...
Has anything changed in recent releases? I can see v2.3.18.0 has some
changes in regards to windows dll paths. Could this 2.3.17 be somewhat
affected?
This bug took me hours today to figure out. I still cant include oiio in
dynamic dll tho. Even when I copy oiio ddls next to PluginA.dll etc it
does not work.
I'm trying to patch vcpkg to use older oiio atm but I've no idea how and
that looks to be fun exercise...
In any case, any ideas?
Regards
Dariusz
--
DARIUSZ MAKOWSKi
CGI-Photographer
07 590 530 854
dari...@dariuszmakowski.com
www.dariuszmakowski.com
_______________________________________________
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
