> git master 8871d5c7a9ecc13f7f86377af8e258372feb1360 replaced mopenssl.pas by
> the files in lib/common/crypto, please test.
>
On Mnday at work where me have a DES co-decoding example.
--
For Developers, A Lot Can Happen
>> The generic type to adopt to amd64 & its OpenSSL client ? Definetely,
>> You know these things better than me. Change this file freely :)
>>
> Do you need all this internal types? For example "cardinal" is used
> for "MD2_INT". Are you sure that is correct on all versions and platforms?
>
Hmm,
On Saturday 14 April 2012 10:42:58 Ivanko B wrote:
> The generic type to adopt to amd64 & its OpenSSL client ? Definetely,
> You know these things better than me. Change this file freely :)
>
git master 8871d5c7a9ecc13f7f86377af8e258372feb1360 replaced mopenssl.pas by
the files in lib/common/crypt
On Saturday 14 April 2012 10:42:58 Ivanko B wrote:
> The generic type to adopt to amd64 & its OpenSSL client ? Definetely,
> You know these things better than me. Change this file freely :)
>
Do you need all this internal types? For example "cardinal" is used
for "MD2_INT". Are you sure that is co
The generic type to adopt to amd64 & its OpenSSL client ? Definetely,
You know these things better than me. Change this file freely :)
2012/4/14, Martin Schreiber :
> On Friday 13 April 2012 14:08:19 IvankoB wrote:
>> > others are not. >What is the criterium?
>>
>> They provide dependencies of o
On Friday 13 April 2012 14:08:19 IvankoB wrote:
> > others are not. >What is the criterium?
>
> They provide dependencies of other "ifdefs" or common dependencies
>
Should the "Longint" types in the bindings be "clong" in most of the cases?
-
On Friday 13 April 2012 14:08:19 IvankoB wrote:
> > others are not. >What is the criterium?
>
> They provide dependencies of other "ifdefs" or common dependencies
>
Is there a reason that BIO_s_fd family is not included apart from forgotten?
Martin
On Friday 13 April 2012 14:08:19 IvankoB wrote:
> > others are not. >What is the criterium?
>
> They provide dependencies of other "ifdefs" or common dependencies
>
For which library versions did you provide the bindings? I get "Function not
found" errors.
Martin
> others are not. >What is the criterium?
>
They provide dependencies of other "ifdefs" or common dependencies
--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your A
On Friday 13 April 2012 12:05:35 IvankoB wrote:
> > I'd like to split the mopenssl.pas monster into separate units. What
> > were the
> > criteria for the different ifdefs? Especially what belongs to always
> > loaded
> > sslutils and what to X509_,EVP_...?
>
> To make the compiled unit (=exe) a bi
> I'd like to split the mopenssl.pas monster into separate units. What
> were the
> criteria for the different ifdefs? Especially what belongs to always
> loaded
> sslutils and what to X509_,EVP_...?
>
>
To make the compiled unit (=exe) a bit smaller if only a set of cypher is
planned to use
Hi,
I'd like to split the mopenssl.pas monster into separate units. What were the
criteria for the different ifdefs? Especially what belongs to always loaded
sslutils and what to X509_,EVP_...?
Martin
--
For Developers,
12 matches
Mail list logo
