On 2/9/2014 9:18 PM, Gisle Vanem wrote:
"Thomas J. Hruska" <shineli...@shininglightpro.com> wrote:
If this ends up being a bug that won't be fixed, then my
recommendation is to build it against VC++. Borland has two
command-line tools called 'impdef' and 'implib' bundled with their
compiler suite(s) that can take almost any DLL and generate .def and
.lib files that can then be used to link against an application in the
native Borland environment. Those tools are even useful with modern
compilers like MinGW.
What you're really saying is that the OP should/could try to mix C-runtimes
(CRT). That normally work fine on things like Linux, but when mixing
CRTs on Windows, it's rather hard to figure out when things don't work
fine. I.e. an app. using Borland's CRT is passing data to/from OpenSSL
DLLs using MS' CRT. This is especially a problem with passing FILE* data
between boundaries. Or a malloc() in CRT-1 and a free() by CRT-2. Other
cases too.
I'm not sure the applink/uplink stuff could be an issue in such a case. The
OP will figure this out if he chooses to follow your advice. IMHO, the
Borland
issue should be fixed anyway.
--gv
Using the BIO interface solves the bulk of the problems related to FILE
pointers and is more cross-platform too.
Not sure about the other issues. Haven't had to deal with them in a while.
--
Thomas Hruska
Shining Light Productions
Home of BMP2AVI and Win32 OpenSSL.
http://www.slproweb.com/
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
