Solution: pass -g so that valgrind/asan can print useful backtraces

Solution: run make with -j5, as now the tests support it.

Solution: don't, libzmq's CI tests are not responsible for testing
libsodium stable releases. Save some time in the CI.

* add define for windows/UWP

* prevent issue with COM references

* gettickcount not available on uwp

* add compiler definitions

* add convenitnece cmake file

* brute force uwp compilation

* fix compiler version

* cosmetics

(msys building is buggy, please be aware, it fails to compile on my
machine) also I modified the buildall.bat/buildbase.bat to use correct
MSVC versions instead of "visual studio 2017"

Fixed path to lib and dll files.

Solution: use pthread API to set the name. For now call every thread
"ZMQ b/g thread". Would be nice to number the I/O threads and name
explicitly the reaper thread, but in reality a bit of internal API
churn would be necessary, so perhaps it's not worth it.
This is useful when debugging a process with many threads.

* cmake WITH_LIBSODIUM option is broken

- Fixed the variable name in platform.hpp.in
- Fixed #if check for randombytes_close() when libsodium is used

* Fixed typo from previous commit

* Reverted compile error fix for randombytes_close()

the root path name specified in this file cause the #2341 problem, the root path name is not need.

Solution: rework the bash test to avoid build failures as intended
and make it an easier one-liner

Solution: use packages on Ubuntu and brews on OSX. The packages and
the brews are always kept up to date, so it's no use to rebuild the
libsodium stable branch manually everytime.

Solution: if available, use eventfd with EFD_CLOEXEC flag to make
the process close the socket on fork+exec

Solution: if available, use epoll_create1 with EPOLL_CLOEXEC flag to
make the process close the socket on fork+exec

Solution: removed Pause

Signed-off-by: Bernd Langpap <Bernd.Langpap@airbus.com>

Solution: Set FD_SETSIZE to 16k for all other build definitions.

Solution: Provide poll() for Windows as well. This is a build option that
defaults to off as the resulting binary will only run on Windows Vista or
newer.

This is not tested with alternative Winsock service providers like VMCI,
but the documentation for WSAPoll does not mention limitations.

On my local machine, throughput improves by ~10 % (20 simultaneous
remote_thr workes to one local_thr, 10 byte messages), while latency
improves by ~30 % (measured with remote/local_lat).

Solution: switch to 4.9

Solution: update CI scripts to use newer r11c from r10e

Solution: use a variable for easier maintenance, in sync with zproject