An argument against combining the two DLL's with a custom build
is that your configuration will be different from everyone else.
Whoever maintains your code after you move on will have to learn
your non-standard configuration. More likely, they'll waste
time undoing your strange setup and going ba
This is off the top of my head, didn't check the sources to make sure, so
validity is 'mostly sure but not entirely'.
Quite a few bits 'n pieces in OpenSSL are 'template' based. (several crypto
methods, a lot of ASN.1 work, an object stack, ...) Think about templates
(wider scope than just the C++
On Tue, Jul 06, 2010, Ger Hobbelt wrote:
> On Tue, Jul 6, 2010 at 9:10 AM, Deckers, Rob wrote:
>
> > If you look in the OpenSSL code (of between the .lib files after build)
> > , you will find 11 so called engines.
> > - Sureware
> > - Padlock
> > - Cswift
> > - 4758cca
> > - Aep
> > - Atalla
>
Thanks,
I am starting to understand the structure.
I now made the same structure in my CMake files.
11 engines and the modules crypto and ssl.
But the Crypto module has a linker problem.
1>-- Build started: Project: openssl.crypto, Configuration: Debug
Win32 --
1>Linking...
1> Creat
On Tue, Jul 6, 2010 at 9:10 AM, Deckers, Rob wrote:
> If you look in the OpenSSL code (of between the .lib files after build)
> , you will find 11 so called engines.
> - Sureware
> - Padlock
> - Cswift
> - 4758cca
> - Aep
> - Atalla
> - Capi
> - Chil
> - Nuron
> - Gmp
> - Ubsec
>
> Does anyone kn
If you look in the OpenSSL code (of between the .lib files after build)
, you will find 11 so called engines.
- Sureware
- Padlock
- Cswift
- 4758cca
- Aep
- Atalla
- Capi
- Chil
- Nuron
- Gmp
- Ubsec
Does anyone know if these are in the Libeay32.dll of in the Ssleay32.dll
?
Rob Deckers
This me
If you're doing your own makefiles (cmake for instance), then anything is
allowed: if 2 dlls feels like trouble to you, I'd suggest building the
entire thing as a library (a.k.a. static library) instead -- can't imagine
what 1 dll does better than 2 of the buggers, but that 's just me -- but
anyway
Anil Tambe wrote:
by 2 dlls .. do you mean libssl and libcrypto ?
Actually they are named: ssleay32.dll and libeay32.dll. To get
'libssl', I copy ssleay32.dll to libssl32.dll during installation (they
are the same thing).
--
Thomas Hruska
Shining Light Productions
Home of BMP2AVI and Win
ent: maandag 05 juli 2010 13:46
To: openssl-users@openssl.org
Subject: Re: Why 2 DLL's for building OpenSSL
by 2 dlls .. do you mean libssl and libcrypto ?
On Mon, Jul 5, 2010 at 4:24 PM, Deckers, Rob
wrote:
I am trying to build OpenSSL by using CMake ( only for windows )
On 07/ 5/10 11:54 AM, Deckers, Rob wrote:
This message and attachment(s) are intended solely for use by the addressee and
may contain information that is privileged, confidential or otherwise exempt
from disclosure under applicable law.
If you are not the intended recipient or agent thereof r
by 2 dlls .. do you mean libssl and libcrypto ?
On Mon, Jul 5, 2010 at 4:24 PM, Deckers, Rob wrote:
>
> I am trying to build OpenSSL by using CMake ( only for windows ) files to
> generate visual studio solutions.
>
> Now I see that OpenSSL results in 2 .dll files.
>
> Is there a special reason
On Mon, 2010-07-05 at 12:54 +0200, Deckers, Rob wrote:
> Is there a special reason why 2 DLL's?
> Could it be combined in just one DLL?
>
one is crypto, with all the crypto stuffs, the other is ssl, with the
SSL/TLS implementation.
I assume they are separated because you could build applications o
I am trying to build OpenSSL by using CMake ( only for windows ) files
to generate visual studio solutions.
Now I see that OpenSSL results in 2 .dll files.
Is there a special reason why 2 DLL's?
Could it be combined in just one DLL?
Greets
Rob Deckers
This message and attachment(s) are
13 matches
Mail list logo
