The testsuite has many so called internal tests, which link statically against libcrypto and/or libssl. All these internal tests are disabled for shared Windows builds, because the names of the static libraries collide with the names of the import libraries for the DLLs.

There has been some discussion about whether the static libraries should be renamed, but that is only an option for the next major release. I would like to suggest a temporary workaround which would be backportable to 1.1.1 and would enable us to activate all internal tests for shared Windows builds.

Instead of renaming the installed libraries, one could build additional static libraries (on windows only) to make the static tests depending on these. One does not even have to rename the static libraries, just place them in a separate directory (e.g. static\libcrypto.lib, static\libssl.lib), to distinguish them from the import libraries. These static libraries would only be used for the internal tests and not installed later on.

If building two library versions is undesired on this notoriously slow platform, then one could add a --static-tests option for windows, which is disabled by default.

References

This request originated from a discussion with @levitte in #7462, see in particular

• Test: link drbgtest statically against libcrypto #7462 (comment)
• Test: link drbgtest statically against libcrypto #7462 (comment)
• Test: link drbgtest statically against libcrypto #7462 (comment)