1. 18 Aug, 2017 1 commit
  2. 24 Mar, 2017 3 commits
  3. 19 Mar, 2017 1 commit
  4. 21 Feb, 2017 1 commit
    • zstang's avatar
      #2341 fix · 3b0dfd52
      zstang authored
      the root path name specified in this file cause the #2341 problem, the root path name is not need.
      3b0dfd52
  5. 11 Jun, 2016 1 commit
    • Michael Lutz's avatar
      Problem: Windows performance is not optimal due to select(). · 7a6ff07a
      Michael Lutz authored
      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).
      7a6ff07a
  6. 25 May, 2016 1 commit
  7. 18 May, 2016 1 commit
  8. 13 May, 2016 6 commits
  9. 12 May, 2016 1 commit
  10. 22 Apr, 2016 1 commit
  11. 30 Mar, 2016 1 commit
  12. 11 Mar, 2016 1 commit
  13. 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
  14. 18 Feb, 2016 1 commit
  15. 07 Feb, 2016 1 commit
  16. 04 Feb, 2016 1 commit
    • Pieter Hintjens's avatar
      Problem: commit a464eec7 really broke VS2015 builds · 86aa7bb1
      Pieter Hintjens authored
      Took me over 8 hours to track down the cause of bizarre link
      errors when building with libsodium. The VS project files are
      not simple things.
      
      Note to self and other maintainers: when someone is obviously
      out of their depth, do not merge their changes to build scripts
      without cynical appraisal.
      
      Solution: undo the damage.
      86aa7bb1
  17. 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
  18. 02 Feb, 2016 3 commits
  19. 01 Feb, 2016 3 commits
  20. 29 Jan, 2016 1 commit
  21. 21 Dec, 2015 4 commits
  22. 05 Nov, 2015 1 commit