Nope, seems like you should be good ..
On Thu, Jul 22, 2021, 20:01 wrote:
> cryptopp-users@googlegroups.com
> <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/cryptopp-users/topics>
> Google
> Groups
> <https://groups.google.com/forum/?
Thanks for the reply!
I tried the master as well from github but got errors. Tomorrow I will send
the logs.
Please, let me know if I have to set some params in order to compile in
win32 with xe5 c++ builder.
Thank you in advance
Il 08/ott/2017 02:07, ha scritto:
> cryptopp-us
I've been having an issue where decrypted data is left in RAM once I'm done
with it. I've traced the problem to decrypting the data to a std::string.
So I've started to move all my code over to use SecByteBlock.
- I wasn't able to figure out how to create a sink that put the encrypted
data so I pa
it works. one thing is that you may have to select release, build, and
then reselect debug if using debug library. you also have to set the
library in import libs etc. and you may have to build the crypt lib also.
lots of docs on code project.com
On Aug 10, 2012 9:04 PM, wrote:
> Today's Topic
The cryptlib*.lib *file is the static library, and you create it yourself
using the crypto++ source code. The you statically link your own code
against this library in order to use the crypto++ features (of course, the
other option is to use the DLL).
This tutorial, although oudated, it's very
