Andy Polyakov wrote:
The Win32 OpenSSL Installation Project is built as follows:
Visual C++ 6 SP6 w/ MASM is used to build the core DLLs and the Visual
C++ libraries.
Borland's IMPLIB tool is used to create libraries from the DLLs for
Builder 4/5/6.
As to your specific problem, I haven't been following it up to this
point, but using FILE * from Builder inside OpenSSL is a great way to
crash the application. Since Visual C++ has its own definition of
FILE and Builder has its own definition, attempting to pass in a
Builder FILE to a VC++ FILE will cause a crash.
Applink is designed to address this very problem. It makes it possible
to pass e.g. Borland FILE* to OpenSSL 0.9>=8 DLL compiled with e.g. VC,
given that end-developer provides glue by compiling ms/applink.c with
her/his application. A.
BIOs are a more appropriate solution, IMO. They are generic and have
better success rates when writing cross-platform code. I have not
encountered any Borland Builder users who have had problems after
switching their code to use BIOs and BIO calls exclusively when
interfacing with OpenSSL.
--
Thomas Hruska
Shining Light Productions
Home of BMP2AVI, Nuclear Vision, ProtoNova, and Win32 OpenSSL.
http://www.slproweb.com/
Ask me about discounts on any Shining Light Productions product!
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
