Whoa,
A thing to keep in mind when you're mixing run-time libraries (and
static linking to a DLL is mixing RTLs, even when you use the same
(threading/etc.) flags for the main app build):
two risks:
1) malloc in one, free in other
2) the FILE * APIs (fopen, etc.)
3) file handl based APIs
#1 is
-
With best regards, Max Terentiev.
Business Software Products.
AMS Development Team.
supp...@bspdev.com
- Original Message -
From: "Mounir IDRASSI"
To:
Sent: Monday, October 05, 2009 12:15 PM
Subject: Re: Compile dlls with Borland compiler OR avoid using VC 2008
Redist
Hi,
You can build OpenSSL dlls that don't require runtime redistribuable
using MS Visual Studio. For that, follow the build instruction and
before calling nmake -f ms\ntdll.mak, edit the file ntdll.mak and
replace the switch /MD by /MT. After the build, you will have dlls that
are statically
Hi,
I suspect BC will have its own runtime libraries to provide similar
generic C runtime functionality.
Yes, but BC can link it inside output .dll.
MS VS should link to but I don't know what compiler option
must be set for it.
__
Max Terentiev wrote:
How to build OpenSSL DLLs using Borland C++ Builder 6 ?
I can successfuly compile and get libeay32.lib/ssleay32.lib files,
but can't understand how to get .dlls ? I was read INSTALL.W32
many times :-)
I can't help with BC specific stuff, but... DLL's are created by a
li
Hi,
How to build OpenSSL DLLs using Borland C++ Builder 6 ?
I can successfuly compile and get libeay32.lib/ssleay32.lib files,
but can't understand how to get .dlls ? I was read INSTALL.W32
many times :-)
I want to re-build OpenSSL because default binaries from
http://www.slproweb.com/products/W
