On Fri, Mar 01, 2024 at 10:10:39PM +0100, Ilya Maximets wrote: > OpenSSL 1.1.0 changed the library names from libeay32 and ssleay32 to > standard libssl and libcrypto. All the versions of OpenSSL that used > old names reached their official EoL, so it should be safe to just > migrate to new names. They can still be supported via premium support > option, but I don't think that is important for us. > > Also, OpenSSL installers for older versions had the following folder > structure: > > C:\OPENSSL-WIN64\ > +---bin > +---include > | +---openssl > +---lib > | libeay32.lib > | ssleay32.lib > +---VC > libeay32MD.lib > libeay32MDd.lib > libeay32MT.lib > libeay32MTd.lib > ssleay32MD.lib > ssleay32MDd.lib > ssleay32MT.lib > ssleay32MTd.lib > > With newer OpenSSL 3+ the structure is different: > > C:\OPENSSL-WIN64 > +---bin > +---include > | +---openssl > +---lib > +---VC > +---x64 > +---MD > | libcrypto.lib > | libssl.lib > +---MDd > | libcrypto.lib > | libssl.lib > +---MT > | libcrypto.lib > | libssl.lib > +---MTd > libcrypto.lib > libssl.lib > > Basically, instead of one generic library in the lib folder and a bunch > of differently named versions of it for different type of linkage, we > now have multiple instances of the library located in different folders > based on the linkage type. So, we have to provide an exact path in > order to find the library. > > 'lib/VC/x64/MT' was chosen in this patch since it is a way used for > building in build-aux/ccl. > MD stands for dynamic linking, MT is static, 'd' stands for debug > versions of the libraries. > > While at it, fixing documentation examples to point to Win64 default > installation folder. > > Signed-off-by: Ilya Maximets <[email protected]>
Acked-by: Simon Horman <[email protected]> _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
