find . -iname '*ssl*.dll'
and I have something like 250 different results.even if I just look for ssleay32.dll I have a ton of results:
./Program Files/Calibre2/app/DLLs/ssleay32.dll
./Program Files/darktable/bin/SSLEAY32.dll
./Program Files/Genshin Impact/ssleay32.dll
./Program Files/Genshin Impact/updateProgram/ssleay32.dll
./Program Files/LibreOffice/program/ssleay32.dll
./Program Files (x86)/Clementine/ssleay32.dll
./Program Files (x86)/Kodi/ssleay32.dll
./Program Files (x86)/GOG Galaxy/ssleay32.dll
./Program Files (x86)/iLok License Manager/ssleay32.dll
./Program Files (x86)/Seafile/bin/SSLEAY32.DLL
./ProgramData/GOG.com/Galaxy/prefetch/desktop-galaxy-updater/ssleay32.dll
./ProgramData/GOG.com/Galaxy/redists/ssleay32.dll
./ProgramData/GOG.com/Galaxy/temp/desktop-galaxy-updater/ssleay32.dll
./ProgramData/Intel/Installer/rs_sdk_2014/cache/4f6dfe1e-80c5-11e6-b7da-2c44fd873b55/plugins/ssleay32.dll
./ue4/UE_4.25/Engine/Binaries/ThirdParty/GoogleInstantPreview/x64/Release/ssleay32.dll
./ue4/UE_4.25/Engine/Binaries/ThirdParty/OpenSSL/Win64/VS2015/ssleay32.dll
./ue4/UE_4.25/Engine/Binaries/ThirdParty/svn/Win64/ssleay32.dll
./Users/blah/AppData/Local/GitHubDesktop/app-0.6.2/resources/app/git/mingw64/bin/ssleay32.dll
./Users/blah/AppData/Local/MEGAsync/ssleay32.dll
./Users/blah/AppData/Local/Microsoft/OneDrive/20.201.1005.0009/ssleay32.dll
./Users/blah/Desktop/Shotcut/ssleay32.dll
./Users/blah/Desktop/smplayer-portable-19.1.0.0/ssleay32.dll
./Users/blah/Documents/PacketSenderPortable/ssleay32.dll
so, "yay", dynamic linking is used. what does this gain ? exactly NOTHING.And yes, this is mostly useful for taking bug fixes, which most mature libraries release without API changes.
Yes, it only applies if you don't make any API (and ABI) changes, but that's what major, minor, patch versioning is for, and stable projects can go a long way on minor and patch versions...