Julien ALLANOS a écrit :
Hello,
I have a Win32 application that uses OpenSSL 0.9.8a, libxml2, xmlsec,
and other libraries. Thus I have to build them all using the same link
configuration (/MD). However I want to be able to debug my application,
and have both Release and Debug versions of every libraries in the same
time on disk. Is there a way to build libeay32D.{lib|dll},
ssleay32D.{lib|dll} and opensslD.exe, using the current win32 build
process?
Thanks,
Actually, I have an application and a DLL. The DLL depends on the
previous libraries. And I just saw the applink.c tip in the FAQ. As I
don't really want to debug OpenSSL, but rather my application and my
DLL, I have included applink.c in my DLL project, compiled it in Debug
mode (/MDd) against a Release (/MD) libeay32, compiled the executable in
Debug mode and ran it. I get the "no OPENSSL_Applink" error again. Any
help please? Thanks.
--
Julien ALLANOS
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
