Re: [cryptopp-users] Re: Any plans for Visual Studio 2017?

[Marcel Raad]

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 entirely sure what's going on.
>
> Does anyone else use VS 2017 CE and successfully build crypto++ 7.0.0 on
> Win10?  If yes, did you have to configure anything to get it to build, and
> link when using it in other projects?
>

what errors do you get? Are you using the same C runtime for Crypto++ and
your project (static vs. dynamic)?

All I had to do was setting the include and library directory and adding
cryptlib.lib to the linker input.

Marcel

>

-- 
You received this message because you are subscribed to "Crypto++ Users". More 
information about Crypto++ and this group is available at 
http://www.cryptopp.com and 
http://groups.google.com/forum/#!forum/cryptopp-users.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [cryptopp-users] Can anyone please help me to get up and running with Visual Studio?

[Marcel Raad]

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
> unresolved symbol errors such as
>

you also have to add the library name under Linker -> Input -> Additional
Dependencies.

Marcel

-- 
You received this message because you are subscribed to "Crypto++ Users". More 
information about Crypto++ and this group is available at 
http://www.cryptopp.com and 
http://groups.google.com/forum/#!forum/cryptopp-users.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [cryptopp-users] Test commit 143f5a307908 under VS2017 or VS2018

[Marcel Raad]

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/commit/143f5a307908
but I could only test Microsoft up to VS2015.

Would someone please test Master using VS2017 or VS2018.


I tested it with Visual Studio 2017 Update 6 Preview 5.0 in C++17 mode with
warnings treated as errors. Builds fine, and verified that it didn't before
that commit. Thanks a lot!

Marcel

-- 
You received this message because you are subscribed to "Crypto++ Users". More 
information about Crypto++ and this group is available at 
http://www.cryptopp.com and 
http://groups.google.com/forum/#!forum/cryptopp-users.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [cryptopp-users] Crypto++ 6.0.0 released

[Marcel Raad]

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 for all the hard work! I'm going to update from
5.6.5 next week.

Marcel

-- 
You received this message because you are subscribed to "Crypto++ Users". More 
information about Crypto++ and this group is available at 
http://www.cryptopp.com and 
http://groups.google.com/forum/#!forum/cryptopp-users.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [cryptopp-users] Call for Crypto++ 6.0 testers

[Marcel Raad]

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 great.

Both 32-bit MinGW-w64 (based on GCC 7) and the classic 32-bit-only
MinGW (based on GCC 6) complain:

g++ -DNDEBUG -g2 -O3 -fPIC -pthread -pipe -c aria-simd.cpp
aria-simd.cpp: In function 'void
CryptoPP::ARIA_ProcessAndXorBlock_Xor_SSSE3(const byte*,
CryptoPP::byte*, const byte*, CryptoPP::word32*)':
aria-simd.cpp:115:76: warning: SSE vector return without SSE enabled
changes the ABI [-Wpsabi]
  const __m128i MASK = _mm_set_epi8(12,13,14,15, 8,9,10,11, 4,5,6,7, 0,1,2,3);

And then many similar errors starting with:
In file included from
C:/msys64/mingw32/lib/gcc/i686-w64-mingw32/7.2.0/include/pmmintrin.h:31:0,
 from
C:/msys64/mingw32/lib/gcc/i686-w64-mingw32/7.2.0/include/tmmintrin.h:31,
 from aria-simd.cpp:22:
C:/msys64/mingw32/lib/gcc/i686-w64-mingw32/7.2.0/include/emmintrin.h:718:1:
error: inlining failed in call to always_inline 'void
_mm_storeu_si128(__m128i_u*, __m128i)': target specific option
mismatch
 _mm_storeu_si128 (__m128i_u *__P, __m128i __B)
 ^~~~
aria-simd.cpp:135:18: note: called from here
  _mm_storeu_si128(M128_CAST(outBlock),
  ^
   _mm_xor_si128(_mm_loadu_si128(CONST_M128_CAST(outBlock)),
   ~
_mm_shuffle_epi8(_mm_load_si128(CONST_M128_CAST(rk)), MASK)));

Cygwin64's clang complains:

clang++ -DNDEBUG -g2 -O3 -D_XOPEN_SOURCE=600 -fPIC -pthread -pipe -c
cryptlib.cpp
clang-5.0: error: unsupported option '-fPIC' for target
'x86_64-unknown-windows-cygnus'

When using MinGW-w64 targeting MSYS from the MSYS2 shell, it compiles
fine, but doesn't link:

g++ -o cryptest.exe -DNDEBUG -g2 -O3 -D_XOPEN_SOURCE=600 -fPIC
-pthread -pipe adhoc.o test.o bench1.o bench2.o validat0.o validat1.o
validat2.o validat3.o validat4.o datatest.o regtest1.o regtest2.o
regtest3.o dlltest.o fipsalgt.o ./libcryptopp.a
regtest3.o:regtest3.cpp:(.rdata$.refptr._ZN8CryptoPP20g_nullNameValuePairsE[.refptr._ZN8CryptoPP20g_nullNameValuePairsE]+0x0):
undefined reference to `CryptoPP::g_nullNameValuePairs'
./libcryptopp.a(asn.o):asn.cpp:(.rdata$.refptr._ZN8CryptoPP15DEFAULT_CHANNELE[.refptr._ZN8CryptoPP15DEFAULT_CHANNELE]+0x0):
undefined reference to `CryptoPP::DEFAULT_CHANNEL'

Visual Studio 2017 Update 6 Preview 2 produces a lot of warning spam.
For every file compiled, it complains:

algparam.h(327): warning STL4006: std::uncaught_exception() is
deprecated in C++17. It is superseded by std::uncaught_exceptions(),
plural.

And one other new warning:

tweetnacl.cpp(249): warning C4146: unary minus operator applied to
unsigned type, result still unsigned

I'd love to look closer into these issues, but I'm on holiday for one
week in a few hours, sorry :-(

Marcel

-- 
You received this message because you are subscribed to "Crypto++ Users". More 
information about Crypto++ and this group is available at 
http://www.cryptopp.com and 
http://groups.google.com/forum/#!forum/cryptopp-users.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [cryptopp-users] Re: Undefined reference to BufferedTransformation

[Marcel Raad]

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

-- 
You received this message because you are subscribed to "Crypto++ Users". More 
information about Crypto++ and this group is available at 
http://www.cryptopp.com and 
http://groups.google.com/forum/#!forum/cryptopp-users.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [cryptopp-users] Undefined reference to BufferedTransformation

[Marcel Raad]

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(sha256Hasher, new CryptoPP::HexEncoder(new
CryptoPP::StringSink(fileFingerprint;


Looks like you're not linking to Crypto++? How are you invoking the
compiler?

Marcel

-- 
You received this message because you are subscribed to "Crypto++ Users". More 
information about Crypto++ and this group is available at 
http://www.cryptopp.com and 
http://groups.google.com/forum/#!forum/cryptopp-users.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [cryptopp-users] cryptopp-565 unclean build with VS2015 cryptopp/wait.h

[Marcel Raad]

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 update for toolset v141 (by default it is v140). I got a
> > compilation warning:
> >
> > 1>[snip]thirdparty-source\cryptopp\wait.h(159): warning C4589:
> Constructor
> > of abstract class 'CryptoPP::WaitObjectsTracer' ignores initializer for
> > virtual base class 'CryptoPP::Tracer'
> > 1>[snip]thirdparty-source\cryptopp\wait.h(159): note: virtual base
> classes
> > are only initialized by the most-derived type
> >
> > Obviously this is just a warning so it is not urgent. I merely report it
> so
> > it might get fixed at some point in the future.
>
> Thanks Andrew. Also see https://github.com/weidai11/cryptopp/issues/214
>

Another attempt: https://github.com/weidai11/cryptopp/commit/c6289edd4481 .

Jeff


Hmm, that shouldn't change anything for now. The latest VS 2017.6's
_MSC_VER is 1913. But better suppress the warning for future versions than
having to suppress it again for every new VS release and having people
complain for new VS versions with older Crypto++ versions :-)

I just tested changing the warning(suppress) to warning(error) and the
warning is still issued in the latest VS preview. But the only suppression
needed is the one in wait.h, there are a few more in .cpp files.

Andrew, you're probably using Crypto++ 5.6.5 without patches? The warning
got suppressed for VS 2017 after the release in git master. Crypto++ 5.6.5
is older than VS 2017.

Marcel

-- 
You received this message because you are subscribed to "Crypto++ Users". More 
information about Crypto++ and this group is available at 
http://www.cryptopp.com and 
http://groups.google.com/forum/#!forum/cryptopp-users.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Any plans for Visual Studio 2017?

[Marcel Raad]

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 subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Please test latest CMake changes

[Marcel Raad]

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 are passed to the linker. Apart from that, everything
works fine for me on Windows (CMake 3.9.2, MSVC) and Ubuntu Xenial (CMake
3.5, g++).

Marcel

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: CryptoPP on Windows XP

[Marcel Raad]

Sorry, forgot to hit "Reply All" instead of Reply...

Am 27.11.2017 09:55 schrieb "Marcel Raad" <marci...@gmail.com>:

Hi Mathijs,


Am 27.11.2017 09:47 schrieb <math...@thimeo.com>:

To support a legacy product I had to build CryptoPP for Windows XP.
However, the default behaviour in config.h causes some trouble with this.

// If the user did not make a choice, then select CryptoNG if either
// Visual Studio 2015 is available, or Windows 10 or above is available.
#if !defined(USE_MS_CRYPTOAPI) && !defined(USE_MS_CNGAPI)
# if (_MSC_VER >= 1900) || ((WINVER >= 0x0A00 /*_WIN32_WINNT_WIN10*/) ||
(_WIN32_WINNT >= 0x0A00 /*_WIN32_WINNT_WIN10*/))
#  define USE_MS_CNGAPI
# else
#  define USE_MS_CRYPTOAPI
# endif
#endif

This means that when building with >= VS2015 but with XP as target,
CryptoPP decides to start using MS_CNGAPI. This is available on the build
system, but not on Windows XP, causing the application to abort on start.
Of course this behaviour can be overridden by manually defining
USE_MS_CRYPTOAPI or USE_MS_CNGAPI, but I think the default behaviour is not
optimal. I don’t see why the version of VS matters in this check.


this has been fixed in this commit:
https://github.com/weidai11/cryptopp/commit/32f715f1d723e2bbb78b44fa9e167d
a64214e2e6

Now only the target Windows version matters, not the Visual Studio version.

Marcel

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: error: 'mutex' in namespace 'std' does not name a type

[Marcel Raad]

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 x86_64
Msys

test@asus-windows MINGW32 ~/cryptopp
$ gcc -dumpmachine
x86_64-pc-msys

Those outputs look wrong to me for a 32-bit machine.


That's really odd. Mine says:
MINGW32 ~
$ gcc -dumpmachine
i686-w64-mingw32

Yours is from the MSYS compiler:
MSYS ~
$ gcc -dumpmachine
x86_64-pc-msys

Marcel

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: error: 'mutex' in namespace 'std' does not name a type

[Marcel Raad]

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/
MzvocLrbIpE/TMCa6LFhCgAJ,
+//  is a compatibility header and it needs _WIN32_WINNT >=
0x501.
+// The work-around should be OK since it won't cross-pollinate into header
files.
+#if defined(__MINGW32__) && (_WIN32_WINNT < 0x501)
+# undef _WIN32_WINNT
+# define _WIN32_WINNT 0x501
+#endif


sorry, I hadn't seen your e-mail until now and have created a pull request
with another option, defining it in the makefile if the user didn't
explicitly specify the target Windows version. Defining it only in
socketft.cpp would be good too, of course.

Note that MinGW-w64 also defines __MINGW32__ and doesn't target Windows
2000 by default. But I think it targets Windows XP anyway by default, so it
would make no difference.

Marcel

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: error: 'mutex' in namespace 'std' does not name a type

[Marcel Raad]

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 needed functions would
not be available. MinGW should really set their default Windows version to
something more current. As nothing needing later Windows versions is used
at all in Crypto++, I wouldn't actively remove it.

Marcel

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: error: 'mutex' in namespace 'std' does not name a type

[Marcel Raad]

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 0x501 to avoid that. This is a
compatibility header needed if you target Windows 2000. Unfortunately
mingw.org MinGW targets Windows 2000 by default AND doesn't provide this
header.

But using MinGW-w64 would be less painful, I think - preferably the
pthreads variant to also avoid the mutex error.

Marcel

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: error: 'mutex' in namespace 'std' does not name a type

[Marcel Raad]

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 were never 
> acknowledged.
> 
> 
> 
> I'm happy to try to support it, but we can't do it without folks testing and 
> filing the bug reports. Without the testers and the bug reports things will 
> likely stay broken.

I'll try testing MinGW again in the coming days. I was very busy in the last 
few weeks, but that should get better now.

Gene, what MinGW flavor are you using? The original 32-bit-only one from 
mingw.org?

The problem is that there's no threading support in libstdc++ when using native 
Windows threads. Compilation works fine for me with the pthreads version of 
MinGW-w64. It should also be possible to use a third-party pthreads library 
with the original mingw.org MinGW as mentioned here [1], but I've never tried 
that yet.

Hopefully it's also possible to distinguish between threading libraries used at 
compile time and set CRYPTOPP_CXX11_SYNCHRONIZATION accordingly. I'll look into 
that soon.

[1] http://www.mingw.org/wiki/pthreads_library

Marcel

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Visual Studio 2017 and ARM64 testing

[Marcel Raad]

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 VS 2017 Update 3 Preview 7.0 and the latest
Windows SDK Preview 10.0.16232 with ARM64 tools. vcvarsall.bat recognizes
arm64 as a valid target, but some of the other scripts it calls don't and
there's no cross compiler for ARM64 shipping with Visual Studio.

Marcel

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Building Crypto++ using MinGW under Windows 10

[Marcel Raad]

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. IIRC, I also successfully used
MinGW-generated *.a files with the MSVC linker once. But mixing both is
probably a bad idea because of the different runtimes used.

Marcel

Am 31.07.2017 7:17 vorm. schrieb "Daniel Karcz" :

Hello Jeffrey,

Yes I would like to get a Windows static library instead of DLL. What
exactly I had to write into bash to get static library.

I also try with command 'make cryptopp.dll' and like you write before, I
think some files are missing because after some compilations make is giving
me this message:
'make: *** No rule to make target 'poly1305.export.o', needed by
'cryptopp.dll'.  Stop.'

Daniel



On Sunday, 30 July 2017 18:24:51 UTC+2, Jeffrey Walton wrote:
>
>
>
> On Saturday, July 29, 2017 at 2:22:46 PM UTC-4, Daniel Karcz wrote:
>>
>> ...
>> Now when I'm in folder with crypto++ files, I'm using like you write
>> before just 'make' command. After few minutes process is done, but I don't
>> have files with *.lib or *.dll extensions in folder. I see libcryptopp.a
>> file - I think this is a static library for unix systems, but I would like
>> to use library under Windows.
>>
>
> I believe you need to 'make cryptopp.dll'. Also see
> https://github.com/weidai11/cryptopp/blob/master/GNUmakefile#L725 .
>
> _IF_ you experience missing source files, then let us know. DLLSRCS in the
> Makefile may not be up to date. We can check-in a change quickly,
>
> But be careful of DLLs on Windows. Usually, you want the static archive.
> Later, you wrap it in your DLL with your API if that's want you want to do.
>
> The FIPS DLL almost always causes problems. Avoid it if possible. Also see
> https://www.cryptopp.com/wiki/FIPS_DLL and https://www.cryptopp.com/wiki/
> Visual_Studio.
>
> Jeff
>
-- 
-- 
You received this message because you are subscribed to the "Crypto++
Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com
.
More information about Crypto++ and this group is available at
http://www.cryptopp.com.
---
You received this message because you are subscribed to the Google Groups
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Building Crypto++ using MinGW under Windows 10

[Marcel Raad]

; did you
mean '-ftemplate-depth-'?
mingw32-make: *** [GNUmakefile:784: cryptlib.o] Error 1


Daniel



On Thursday, 27 July 2017 21:48:08 UTC+2, Marcel Raad wrote:

> 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 try compiling with -std=gnu++98.
>
> Marcel
>
> Am 27.07.2017 9:01 nachm. schrieb "Daniel Karcz" <daniel...@gmail.com>:
>
> Hi,
>
> Can somebody provide GCC's make commands for building static and dynamic
> libraries under Windows using MinGw.
>
> I've tried with commands what I found for example on this discussions
> group, but I always getting couple of errors connected with 'mutex'.
>
> Thanks in advance,
> Daniel
>
> --
> --
> You received this message because you are subscribed to the "Crypto++
> Users" Google Group.
> To unsubscribe, send an email to cryptopp-user...@googlegroups.com.
>
> More information about Crypto++ and this group is available at
> http://www.cryptopp.com.
> ---
> You received this message because you are subscribed to the Google Groups
> "Crypto++ Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to cryptopp-user...@googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
-- 
You received this message because you are subscribed to the "Crypto++
Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com
.
More information about Crypto++ and this group is available at
http://www.cryptopp.com.
---
You received this message because you are subscribed to the Google Groups
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Building Crypto++ using MinGW under Windows 10

[Marcel Raad]

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 try compiling with -std=gnu++98.

Marcel

Am 27.07.2017 9:01 nachm. schrieb "Daniel Karcz" :

Hi,

Can somebody provide GCC's make commands for building static and dynamic
libraries under Windows using MinGw.

I've tried with commands what I found for example on this discussions
group, but I always getting couple of errors connected with 'mutex'.

Thanks in advance,
Daniel

-- 
-- 
You received this message because you are subscribed to the "Crypto++
Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com
.
More information about Crypto++ and this group is available at
http://www.cryptopp.com.
---
You received this message because you are subscribed to the Google Groups
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Successful test results with recent additions. Still need Windows Phone, WIndows Store and MinGW

[Marcel Raad]

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 -pipe -c sha.cpp
ERROR: failed to generate sha1rnds4 instruction
ERROR: failed to generate sha1nexte instruction
ERROR: failed to generate sha1msg1 instruction
ERROR: failed to generate sha1msg2 instruction
ERROR: failed to generate sha256rnds2 instruction
ERROR: failed to generate sha256msg1 instruction
ERROR: failed to generate sha256msg2 instruction

And this assertion in the Debug C++03/11/14/17 builds:
Testing RoundUpToMultipleOf/RoundDownToMultipleOf...
passed: RoundUpToMultipleOf, byte, no overflow
passed: RoundUpToMultipleOf, byte, no overflow
passed: RoundUpToMultipleOf, byte, no overflow
passed: RoundUpToMultipleOf, byte, no overflow
passed: RoundUpToMultipleOf, byte, no overflow
passed: RoundUpToMultipleOf, byte, overflow
passed: RoundUpToMultipleOf, word16, no overflow
passed: RoundUpToMultipleOf, word16, no overflow
passed: RoundUpToMultipleOf, word16, no overflow
passed: RoundUpToMultipleOf, word16, no overflow
passed: RoundUpToMultipleOf, word16, no overflow
passed: RoundUpToMultipleOf, word16, overflow
passed: RoundUpToMultipleOf, word32, no overflow
passed: RoundUpToMultipleOf, word32, no overflow
passed: RoundUpToMultipleOf, word32, no overflow
passed: RoundUpToMultipleOf, word32, no overflow
passed: RoundUpToMultipleOf, word32, no overflow
passed: RoundUpToMultipleOf, word32, overflow
passed: RoundUpToMultipleOf, word64, no overflow
passed: RoundUpToMultipleOf, word64, no overflow
passed: RoundUpToMultipleOf, word64, no overflow
passed: RoundUpToMultipleOf, word64, no overflow
passed: RoundUpToMultipleOf, word64, no overflow
passed: RoundUpToMultipleOf, word64, overflow
Assertion failed: misc.h(981): RoundUpToMultipleOf
ERROR: failed to execute validation suite

And MSYS had these errors:

Testing: X86 AES-NI code generation
g++ -DNDEBUG -g2 -O2 -msse -msse2 -D_XOPEN_SOURCE=700 -fPIC -m64 -pipe
-c rijndael.cpp
ERROR: failed to generate aesenc instruction
ERROR: failed to generate aesenclast instruction
ERROR: failed to generate aesdec instruction
ERROR: failed to generate aesdeclast instruction
ERROR: failed to generate aesimc instruction
ERROR: failed to generate aeskeygenassist instruction

Testing: X86 carryless multiply code generation
g++ -DNDEBUG -g2 -O2 -msse -msse2 -D_XOPEN_SOURCE=700 -fPIC -m64 -pipe
-c gcm.cpp
ERROR: failed to generate pclmullqhq instruction
ERROR: failed to generate pclmullqlq instruction

Testing: X86 RDRAND and RDSEED code generation
g++ -DNDEBUG -g2 -O2 -msse -msse2 -D_XOPEN_SOURCE=700 -fPIC -m64 -pipe
-c rdrand.cpp
Verified rdrand and rdseed machine instructions

Testing: X86 CRC32 code generation
g++ -DNDEBUG -g2 -O2 -msse -msse2 -D_XOPEN_SOURCE=700 -fPIC -m64 -pipe
-c crc.cpp
ERROR: failed to generate crc32l instruction
ERROR: failed to generate crc32b instruction

Testing: X86 SHA code generation
g++ -DNDEBUG -g2 -O2 -msse -msse2 -D_XOPEN_SOURCE=700 -fPIC -m64 -pipe
-c sha.cpp
ERROR: failed to generate sha1rnds4 instruction
ERROR: failed to generate sha1nexte instruction
ERROR: failed to generate sha1msg1 instruction
ERROR: failed to generate sha1msg2 instruction
ERROR: failed to generate sha256rnds2 instruction
ERROR: failed to generate sha256msg1 instruction
ERROR: failed to generate sha256msg2 instruction


> OK thanks. Try this before you spend time on it:
> https://github.com/weidai11/cryptopp/commit/ddcd70b152964db5

Thanks, 9dcb72f9e5309b19fd72fcf14672a652bbd63b83 fixed the build.

Marcel

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Successful test results with recent additions. Still need Windows Phone, WIndows Store and MinGW

[Marcel Raad]

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 Decompressors...
passed: filenames, filetimes and comments
passed: 128 zips and unzips
Assertion failed: zinflate.cpp(560): DecodeBody
ERROR: failed to execute validation suite

Which is this assert:
// TODO: this surfaced during fuzzing. What do we do???
CRYPTOPP_ASSERT(m_distance < COUNTOF(distanceExtraBits));
if (m_distance >= COUNTOF(distanceExtraBits))
  throw BadDistanceErr();

MinGW64 and MSYS are still running.

I had build problems for Windows Store/Phone that I'm going to look
into today if I find enough time. Do you only need Store/Phone or also
Windows Universal App builds?

Marcel

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Archive VC++ 6.0 workspace and project files?

[Marcel Raad]

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 how to get an English header for quotes in Google Groups? 
Now I got an English web interface, but the header for quotes is still in 
German...)

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.