On Jan 23 21:35, Kurt Roeckx wrote: > On Sat, Jan 23, 2016 at 09:27:58PM +0100, Corinna Vinschen wrote: > > > > Last but not least, we have another problem with enginesdir. To allow a > > rolling release cycle, we have to support multiple versions of openssl > > in parallel. The problem here is that the enginesdir needs to be > > versioned to allow per-openssl version engines. The build scripts don't > > allow for this. Right now we're using a patch as the below one to tweak > > the configury to allow specifying the engines dir during build time. > > Would it hurt terribly to include something like the below patch? > > In general, I would like to have a directory for the engines that > relates to OSSL_DYNAMIC_OLDEST.
That probably won't work for Cygwin. The engines are linked against the versioned DLLs of the OpenSSL version they have been built for, Even assuming binary compatibility, an engine linked against openssl-1.0 will pull in openssl-1.0 DLLs, even when loaded from openssl-1.1. We have to keep the engines separate. Corinna
signature.asc
Description: PGP signature
_______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
