1. 22 Feb, 2017 1 commit
    • boringuy's avatar
      cmake WITH_LIBSODIUM option is broken (#2349) · d6f4263c
      boringuy authored
      * 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()
      d6f4263c
  2. 27 Dec, 2016 2 commits
  3. 26 Dec, 2016 2 commits
  4. 21 Apr, 2016 2 commits
  5. 10 Apr, 2016 1 commit
  6. 11 Feb, 2016 4 commits
    • Luca Boccassi's avatar
      Problem: CI use of sodium or nacl is confusing · 9393f063
      Luca Boccassi authored
      Solution: establish a matrix of CI options. On one axis we have the
      build system (autotools, cmake, android) and on the other axis we
      have the encryption options (tweetnacl, libsodium or none).
      9393f063
    • Luca Boccassi's avatar
      Problem: typo in CMake platform.hpp breaks build · 01eb5807
      Luca Boccassi authored
      Solution: use ZMQ_USE_TWEETNACL as a define as expected instead of
      HAVE_TWEETNACL
      01eb5807
    • Luca Boccassi's avatar
      Problem: CMake CI build still clones libsodium · 0bdc5d04
      Luca Boccassi authored
      Solution: avoid cloning libsodium, default build is tweetnacl
      0bdc5d04
    • Pieter Hintjens's avatar
      Problem: tweetnacl sources are a mess · f8ed793f
      Pieter Hintjens authored
      - they have no copyright / license statement
      - they are in some randomish directory structure
      - they are a mix of postable and non-portable files
      - they do not conform to conditional compile environment
      
      Overall, it makes it rather more work than needed, in build scripts.
      
      Solution: clean up tweetnacl sauce.
      
      - merged code into single tweetnacl.c and .h
      - standard copyright header, DJB to AUTHORS
      - moved into src/ along with all other source files
      - all system and conditional compilation hidden in these files
      - thus, they can be compiled and packaged in all cases
      - ZMQ_USE_TWEETNACL is set when we're using built-in tweetnacl
      - HAVE_LIBSODIUM is set when we're using external libsodium
      f8ed793f
  7. 08 Feb, 2016 1 commit
  8. 05 May, 2015 1 commit
  9. 26 Apr, 2015 1 commit
  10. 11 Mar, 2015 1 commit
  11. 12 Feb, 2015 2 commits
  12. 06 Feb, 2015 2 commits
  13. 18 Mar, 2014 1 commit
  14. 17 Mar, 2014 1 commit
    • Frank's avatar
      fix test_fork · 9dc890c5
      Frank authored
      * was problem on debian/wheezy
      9dc890c5
  15. 17 Feb, 2014 1 commit
    • Olaf Mandel's avatar
      Remove duplicate poller decision making · 48b50cef
      Olaf Mandel authored
      The decision about the poller mechanism to use (select, poll, ...)
      was done twice: once by the build system and once by the code in
      poller.hpp. As the build-system can actually detect the mechanisms
      available, prefer that result to the hard coded defaults in
      poller.hpp.
      
      At the same time, remove the duplicate detection of select() vs.
      poll()-variant from proxy.cpp, signaler.cpp and zmq.cpp.
      
      This patch has not been tested on many build platforms: especially
      the cmake build needs testing / patching. For the other builds,
      hard code the result as these these are all Windows platforms.
      48b50cef
  16. 06 Dec, 2013 1 commit
  17. 14 Jul, 2013 1 commit
  18. 27 Jan, 2013 1 commit
  19. 02 Jan, 2013 3 commits