On 6/24/2010 5:02 PM, Yaakov (Cygwin/X) wrote: > Do you know yet what the actual DLL names are going to be? libkio > dlopen()s these instead of linking against them, so I want to fix these > for my next KDE release.
When I built it for (a cygwin fork that shall not be named), they were: lib/openssl/engines-1.0.0/libubsec.so lib/openssl/engines-1.0.0/libsureware.so lib/openssl/engines-1.0.0/libpadlock.so lib/openssl/engines-1.0.0/libnuron.so lib/openssl/engines-1.0.0/libgost.so lib/openssl/engines-1.0.0/libgmp.so lib/openssl/engines-1.0.0/libcswift.so lib/openssl/engines-1.0.0/libchil.so lib/openssl/engines-1.0.0/libcapi.so lib/openssl/engines-1.0.0/libatalla.so lib/openssl/engines-1.0.0/libaep.so lib/openssl/engines-1.0.0/lib4758cca.so lib/openssl/engines-1.0.0/ bin/msys-ssl-1.0.0.dll bin/msys-crypto-1.0.0.dll (obviously those last two would be "cygssl-1.0.0.dll" and "cygcrypto-1.0.0.dll") Now, that build used the following patches make-dummy-cert* Makefile.certificate openssl-0.9.6-x509.patch openssl-0.9.7-beta5-version-add-engines.patch openssl-0.9.8a-defaults.patch-1.0.0 openssl-0.9.8a-enginesdir.patch-1.0.0 openssl-0.9.8-beta6-icpbrasil.diff openssl-0.9.8e-crt.patch derived/taken from Mandriva. But at most those patches only affected the engine path, not the DLL names. -- Chuck