1. 13 May, 2016 2 commits
  2. 12 May, 2016 1 commit
  3. 21 Feb, 2016 1 commit
    • Osiris's avatar
      Problem: Several problems found by Coverity Static Analyzer · b3d5fa63
      Osiris authored
      Solution: The Coverity Static Code Analyzer was used on libzmq code and found
      many issues with uninitialized member variables, some redefinition of variables
      hidding previous instances of same variable name and a couple of functions
      where return values were not checked, even though all other occurrences were
      checked (e.g. init_size() return).
      b3d5fa63
  4. 03 Feb, 2016 2 commits
    • Pieter Hintjens's avatar
      Problem: MSVC build does not detect libsodium · 31d181ef
      Pieter Hintjens authored
      Caused by error in last commit which used HAVE_LIBSODIUM instead
      of HAVE_SODIUM.
      
      Solution: use HAVE_LIBSODIUM as we do in other configure scripts.
      
      The project is called 'libsodium' and not 'sodium'.
      31d181ef
    • Pieter Hintjens's avatar
      Problem: can't build without libsodium from command line (MSVC) · 6a9af8ed
      Pieter Hintjens authored
      There is an option to enable/disable libsodium via the Visual Studio
      UI. This is not practical for command-line usage (via msbuild).
      
      Solution: add configure.bat that searches for libsodium in sibling
      directory to libzmq; if it finds it, defines HAVE_LIBSODIUM 1.
      
      This is consistent with zproject, which has the same problem and
      is getting the same solution for all dependency resolution on
      Windows.
      
      Note that this approach also provides a way to support tweetnacl
      via a configure option.
      
      Also, removed duplicate props files and re-copy in configure.bat
      as it was an insane nightmare to update these by hand. (and not
      clear that they were identical. Now it's forced.)
      6a9af8ed
  5. 02 Feb, 2016 2 commits