1. 24 Mar, 2017 3 commits
  2. 12 May, 2016 1 commit
  3. 31 Mar, 2016 1 commit
    • Matt Powley's avatar
      Use vs2015 MSBuild property sheets in older projects · 0e405a5a
      Matt Powley authored
      All the older (vs2010 -> vs2013) projects had copies of the Visual Studio 2015 MSBuild applied to them when running the 'configure.bat' batch file. Any modifications to a property sheet was not applied to the other Visual Studio versions' projects unless the batch file was re-executed.
      
      * Modified the older projects to reference the Visual Studio 2015 property sheets so changes are immediately applied
      * Removed the batch file copy steps (which left the repository very dirty after execution)
      0e405a5a
  4. 21 Feb, 2016 3 commits
    • 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
    • Osiris's avatar
      Problem: Visual Studio Toolset was incorrectly set in VCXPROJ files · 4fca95a5
      Osiris authored
      Solution: Corrected Toolset setting where needed and inprove compilation speed
      by adding defintion of WIN32_LEAN_AND_MEAN prior to any Windows specific
      include files, which skips non-essential definitions during compilation.
      4fca95a5
    • Osiris's avatar
      roblem: Visual Studio Toolset was incorrectly set in VCXPROJ files · b4784d95
      Osiris authored
      Solution: Corrected Toolset setting where needed and inprove compilation speed
      by adding defintion of WIN32_LEAN_AND_MEAN prior to any Windows specific
      include files, which skips non-essential definitions during compilation.
      b4784d95
  5. 03 Feb, 2016 1 commit
    • 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
  6. 21 Dec, 2015 1 commit
  7. 05 Jun, 2014 1 commit
  8. 31 May, 2014 1 commit
  9. 21 May, 2014 1 commit
  10. 13 May, 2014 1 commit
  11. 12 May, 2014 1 commit
  12. 06 May, 2014 1 commit
  13. 15 Apr, 2014 1 commit
  14. 09 Apr, 2014 1 commit
  15. 08 Apr, 2014 1 commit
  16. 06 Apr, 2014 1 commit
  17. 30 Mar, 2014 1 commit