Why it's required to ship libcrypto-1_1.dll and libssl-1_1.dll along with application in static linking #12517
Comments
|
The "static libraries" are so called import libraries. On their own, they are just stubs to connect the application with the DLLs. That's why you have to have the DLLs in a place that Windows knows about, and the easiest is to have them alongside the application that uses them. This is quite special with Windows. |
kiyolee
pushed a commit
to kiyolee/openssl
that referenced
this issue
Jul 23, 2020
The condition in test_error_checks() was inverted, so the test succeeded as long as error_check() failed. Incidently, error_check() contained several bugs that assured it always failed, thus giving overall drbg test success. Remove the broken explicit zero check. RAND_DRBG_uninstantiate() cleanses the data via drbg_ctr_uninstantiate(), but right after that it resets drbg->data.ctr using RAND_DRBG_set(), so TEST_mem_eq(zero, sizeof(drbg->data)) always failed. (backport from openssl#11195) Signed-off-by: Vitezslav Cizek <vcizek@suse.com> Reviewed-by: Paul Dale <paul.dale@oracle.com> Reviewed-by: Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com> (Merged from openssl#12517)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why it's required to ship libcrypto-1_1.dll and libssl-1_1.dll alon with application in static linking
version : OpenSSL 1.1.1
I built openssl static libraires and linked in my application.
When i tried to start the application it's giving error libcrypto-1_1.dll and libssl-1_1.dll missing.
If i linked with static libraries why it's required to ship dll's.
OPENSSL Configuration:
Command line (with current working directory = .):
Perl information:
Enabled features:
Disabled features:
Config target attributes:
Recorded environment:
Makevars:
NOTE: These variables only represent the configuration view. The build file
template may have processed these variables further, please have a look at the
build file for more exact data:
makefile
build file:
build file templates:
The text was updated successfully, but these errors were encountered: