Am Donnerstag, 8. September 2016 23:01:10 UTC+2 schrieb Jeffrey Walton:
> Does anyone have thoughts or objections > to the archive?
Could the VS2010 solution be made the default in one of the next releases? I
really hope that most people are using VS2010+ nowadays.
Marcel
(And does anyone know
Hi Jeff,
2017-05-17 17:53 GMT+02:00 Jeffrey Walton :
> We still need Windows Phone, WIndows Store and MinGW tested. If anyone
> specializes in the platforms, then please make a testing pass using master.
With MinGW32, I got this in all 16 debug configurations:
Testing Compressors and Decompressor
2017-05-18 14:38 GMT+02:00 Jeffrey Walton :
> It can be sidestepped with:
>
> CXXFLAGS="-DNDEBUG -g2 -O2 -DCRYPTOPP_COVERAGE" make
Thanks, the MinGW32 tests passed with this.
MinGW64 had this additional failure:
Testing: X86 SHA code generation
g++ -DNDEBUG -g2 -O2 -msse -msse2 -march=native -p
Hi Daniel,
which flavor and version of MinGW are you using? The original version from
mingw.org or MinGW-w64?
If you're using MinGW-w64, you should choose POSIX rather than Windows
threads to get std::mutex. If you're using the original MinGW, you probably
need a third-party threading library. Or
d68'
g++: error: unrecognized command line option '-wd186'
g++: error: unrecognized command line option '-wd279'
g++: error: unrecognized command line option '-wd327'
g++: error: unrecognized command line option '-wd161'
g++: error: unrecognized command line o
Hi Daniel,
(sorry to everyone for top-posting all the time and not being able to quote
correctly, I have to use the Gmail Android App at the moment, which won't
let me do that)
I think libcryptopp.a is the one you want as a static library. The MinGW
linker accepts both lib*.a and *.lib files. IIR
Hi,
Am 01.08.2017 6:57 vorm. schrieb "Jeffrey Walton" :
I was thinking we could nuke MMX and ISSE, and make Whirlpool's minimum
SSE2.
Any objections?
if this is only about Whirlpool, I don't have any objections. But we still
have to support Pentium II at work unfortunately, which has MMX and P
Am 31.07.2017 9:16 nachm. schrieb "Jeffrey Walton" :
I'd like to get the library tested under VS2017. I have the build tools
installed, but I have not been able to get a 64-bit ARM developer prompt.
I don't think that's possible yet unless you have early access to those
tools. I have the latest
On Saturday, November 4, 2017 at 10:36:30 PM UTC+1, Jeffrey Walton wrote:
> I tired to setup a MinGW testing environment several times but it either (1)
> never worked or (2) broke immediately. On the rare occasions I could compile
> and link I was able to file some MinGW bug reports but they wer
Hi Gene,
Am 06.11.2017 18:55 schrieb :
g++ -DNDEBUG -g2 -O3 -pthread -pipe -c socketft.cpp
socketft.cpp:36:23: fatal error: wspiapi.h: No such file or directory
# include
^
compilation terminated.
make: *** [socketft.o] Error 1
you can define _WIN32_WINNT to at least 0
Hi Jeff,
Am 06.11.2017 19:29 schrieb "Jeffrey Walton" :
Should we remove that header or comment it out? I don't know anyone
developing on Windows 2000 anymore. Windows XP and Windows 2003 are
the floors for the development shops I work with.
unfortunately that wouldn't help either as then the n
Hi Jeff,
Am 06.11.2017 20:20 schrieb "Jeffrey Walton" :
How does this fancy you:
$ git diff
diff --git a/socketft.cpp b/socketft.cpp
index 454eaa5..20cda22 100644
--- a/socketft.cpp
+++ b/socketft.cpp
@@ -30,6 +30,14 @@
# include
#endif
+// From http://groups.google.com/d/msg/cryptopp-users/
Am 08.11.2017 00:29 schrieb "Jeffrey Walton" :
The 32-bit prompt looks off to me. It says MINGW32 as expected, but the
compiler is building for (targeting) 64-bit executable:
test@asus-windows MINGW32 ~/cryptopp
$ uname -a
MINGW32_NT-6.3 asus-windows8 2.9.0(0.318/5/3) 2017-09-13 23:16
Sorry, forgot to hit "Reply All" instead of Reply...
Am 27.11.2017 09:55 schrieb "Marcel Raad" :
Hi Mathijs,
Am 27.11.2017 09:47 schrieb :
To support a legacy product I had to build CryptoPP for Windows XP.
However, the default behaviour in config.h causes some trouble w
Am 28.11.2017 02:53 schrieb "Jeffrey Walton" :
We added SM3, SM4, Simon and Speck recently. Changes were made to the Cmake
files at https://github.com/noloader/cryptopp-cmake.
Would someone please test them.
Using Visual Studio 2017 on Windows, I get a lot of warnings because
compiler options a
Am 30.11.2017 04:10 schrieb "MalleeswaraReddy s" :
cryptopp.lib(rijndael.obj) : error LNK2019: unresolved external symbol
Rijndael_Enc_AdvancedProcessBlocks referenced in function "public: virtual
unsigned __int64 __cdecl
CryptoPP::Rijndael::Enc::AdvancedProcessBlocks(unsigned
char const *,unsigne
Hi Andrew,
Am 21.12.2017 10:34 schrieb "Andrew Marlow" :
Are there any plans for cryptopp to support VS2017 please?
the current master branch does support it. I'm using version 5.6.5 + some
patches from git master with VS2017 myself.
Marcel
--
--
You received this message because you are su
Am 12.01.2018 14:26 schrieb "Jeffrey Walton" :
On Friday, January 12, 2018 at 8:03:42 AM UTC-5, Jeffrey Walton wrote:
>
> On Fri, Jan 12, 2018 at 7:28 AM, Andrew Marlow
> wrote:
> > Hello everyone,
> >
> > I just tried to build cryptopp 565 on Windows 10 using Visual Studio
> 2017
> > with the
Am 13.01.2018 14:20 schrieb :
Does anybody know why I'm getting this error? https://pastebin.com/YeGA4dgN
I just want make fingerprint of a file and put it into string.
CryptoPP::SHA256 sha256Hasher;
CryptoPP::FileSource createFileFingerprint(filePath.c_str(), true, new
CryptoPP::HashFilter(sha2
Am 13.01.2018 14:29 schrieb :
Using the G++ option *-lcryptopp*. The program will compile if I keep
the *CryptoPP::SHA256
sha256Hasher;* and comment the FileSource.
OK, now that's strange. What version of Crypto++ is this? Are you building
it yourself or are you using a system package?
Marcel
2018-01-19 17:04 GMT+01:00 Jeffrey Walton :
> If you have some time, then please
> test Master on your favorite platform.
MinGW64 and Cygwin64 with GCC look good. All GCC and clang versions
available in the Linux systems coming with Windows 10 (Ubuntu Xenial,
openSUSE 42, SLES 12) seem to work gre
Hi Jeff,
Am 22.01.2018 23:02 schrieb "Jeffrey Walton" :
Crypto++ 6.0.0 was released today. The 6.0.0 release was a major release.
The release included two CVE fixes.
The release notes and list of issues fixed can be found at
http://www.cryptopp.com/release600.html.
great, thank you very much f
Hi Jeff,
Am 21.02.2018 17:21 schrieb "Jeffrey Walton" :
GCC 8 is experimental, but we made a c++17 testing pass. Things were very
noisy due to deprecated std::uncaught_exception. Also see
https://github.com/weidai11/cryptopp/issues/590 .
We cleared it at https://github.com/weidai11/cryptopp/comm
Hi,
schrieb am Di., 27. März 2018, 20:15:
> After installing Universal runtime into VS 2017 and successfully compiling
> Cryptlib, how do I reference it from my VS projects? I tried adding
> *\cryptopp\Win32\Output\Debug\
> *to the lib path of the project properties, but VS still threw 121
> un
Hi James,
James Young schrieb am Fr., 5. Okt. 2018, 17:19:
> But when I try to use it in a project, after adding the include path and
> the output path with the x64 cryptlib.lib file, I always get linker
> errors. I use the same SDK version and same x64 config for my projects, so
> I'm not enti
25 matches
Mail list logo