[openssl] libcrypto-3-x64.dll relie on absolute path for legacy.dll #36482
Labels
category:port-bug
The issue is with a library, which is something the port should already support
Stale
Library
OpenSSL 3.2.0 used to build PoDoFo 0.10.3
Architecture
x64-windows
Build env
Tested on Windows 10 22H2 and Windows 11 23H2
vcpkg 2024-01-11-710a3116bbd615864eef5f9010af178034cb9b44
Problem : Discussed in #36403
Originally posted by cvermot January 27, 2024
I used vcpkg to deploy PoDoFo library in a MSVC project. This library use among other things openssl.
When I execute my application on my dev machine, all is working. When I deploy this app on my target machine, I get an error "The application was unable to start correctly (0xc0000142)".
I first thought that it was a DLL problem, so I double checked that all required DLL was on my app side. Everything seemed to be there.
I used Dependency Walker's profiling function which gave me the answer: the openSSL
libcrypto-3-x64.dll
library rely onlegacy.dll
, which seems to be linked with the absolute path of my vcpkg installation on my development computer (DW give me the exact path of legacy.dll on my dev computer) ! If I recreate on my target computer the exact path of legacy.dll on my development computer, my app run !DW error :
The text was updated successfully, but these errors were encountered: