[openssl-dev] Question about dynamically loadable engines on Cygwin / Mingw
Corinna Vinschen
vinschen at redhat.com
Mon Feb 15 10:50:45 UTC 2016
Hi Richard,
On Feb 15 01:11, Richard Levitte wrote:
> Hi,
>
> I've got a question to the Cygwin / Mingw community, regarding the
> naming of dynamic engines.
>
> >From looking at Makefile.shared et al, the engines get the same kind
> of prefixes as a standard shared library (but without the accompanying
> import library, of course). So the capi engine gets named like this:
>
> Cygwin: cygcapi.dll
I can't speak for Mingw, but on Cygwin the modules are called libFOO.so,
e.g.
/usr/lib/openssl-1.0.2/engines/libcapi.so
I hope the changes to the build system will keep this intact.
> This is assuming, btw, that no one mixes the different Windows POSIX
> layers on top of each other. If such mixes are commonplace, it's
> worth considering, of course...
No such mixing is possible due to dependency issues, nor is it
supported. You can try but it will not work as desired. Ideally just
handle Cygwin as a POSIX system with a few quirks (like having the DLLs
in /usr/bin instead of /usr/lib), but otherwise disjunct from native
Windows environments. POSIX, not Windows.
Thanks,
Corinna
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://mta.openssl.org/pipermail/openssl-dev/attachments/20160215/f7a07547/attachment.sig>
More information about the openssl-dev
mailing list