On Feb 15 13:03, Richard Levitte wrote:
> So here is what I'm thinking...
> 
> - engines in 1.1 should be named FOO.{suffix} (for an engine FOO and
>   whatever suffix is conventional on the platform at hand, be it .so,
>   .dll, .sl, .dylib...)
> - the OpenSSL DSO module should be changed to have the DSO suffix
>   configured instead of having it hardcoded as it is right now (the
>   template framework we use makes that real easy, see how
>   crypto/include/internal/bn_conf.h is generated as an example).
> - the OpenSSL ENGINE module should be changed to tell the DSO module
>   not to prefix the received file name with "lib" (which I suspect is
>   the primary reason for the install hack you mentioned above).
> 
> That way, we would have engines that look like DSOs and not like
> shared libraries.  On cygwin, that would be something like "capi.dll",
> on MacOS it would be "capi.dylib", on most other Unixen it would be
> "capi.so".  My intention is to have this work smoothly and
> consistently, without having to resort to all kinds of weird install
> hacks or whatnot.
> 
> Does that sounds like an acceptable change to you?

Any method being platform independent because implementation details are
hidden under the hood sounds perfect to me.


Thanks,
Corinna

Attachment: signature.asc
Description: PGP signature

-- 
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Reply via email to