Re: Crypto++ 5.6.5 and Valgrind

Hi, Thanks a lot for your answer. > I've just upgraded from an older version to Crypto++ 5.6.5 and my > Valgrind is seriously unhappy about it. Even the "cryptest.exe v" > command crashes with "Illegal instruction" (details on request) when > calling it with > > > [] > We

Re: Crypto++ 5.6.5 and Valgrind

On Wed, Nov 29, 2017 at 9:34 AM, Jeffrey Walton wrote: > On Wed, Nov 29, 2017 at 9:16 AM, Ingo Naumann wrote: >> ... >> ... >> So now I've upgraded to valgrind-3.14.0.GIT (cloned ten minutes ago) but it >> yields the same result. I'm hitting illegal

Change Doxygen comment stle from //! to ///

Hi Everyone, I'd like to change the Doxygen comment style from //! to ///. It will be a massive change, but it should help some tools. Visual Studio appears to be a lost cause. I know it does not work with //! style. It appears Microsoft will only provide Intellisense with C# style comments,

Re: Crypto++ 5.6.5 and Valgrind

On Wed, Nov 29, 2017 at 9:16 AM, Ingo Naumann wrote: > ... > We work around it by building Valgrind from sources. Its fairly easy once > you install the packages "automake autoconf libtool". Also see > http://valgrind.org/downloads/repository.html. > > Hmmm. I had built

Re: Crypto++ 5.6.5 and Valgrind

Hi, >> You might be able to work around it by removing the `-march=native` >> from CXXFLAGS. Open GNUmakefile and delete the line that adds it. >> However, you will loose a fair amount of performance because the >> source files depend on some of the options included in >> `-march=native`. Wo-ho!

Re: Having trouble compiling cryptopp with vs 2013 for x86_64

On linux and mac , crypto cpp library with Qt worked correctlry. On windows msvc 2015 64 bit + Qt 5.9 getting error. -- "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\nmake.exe" -f Makefile.Release