libzmq/builds/msvc/vs2013
Pieter Hintjens 6a9af8ed62 Problem: can't build without libsodium from command line (MSVC)
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.)
2016-02-03 22:44:06 +01:00
..
inproc_lat Problem: can't build without libsodium from command line (MSVC) 2016-02-03 22:44:06 +01:00
inproc_thr Problem: can't build without libsodium from command line (MSVC) 2016-02-03 22:44:06 +01:00
libzmq Problem: can't build without libsodium from command line (MSVC) 2016-02-03 22:44:06 +01:00
local_lat Problem: can't build without libsodium from command line (MSVC) 2016-02-03 22:44:06 +01:00
local_thr Problem: can't build without libsodium from command line (MSVC) 2016-02-03 22:44:06 +01:00
remote_lat Problem: can't build without libsodium from command line (MSVC) 2016-02-03 22:44:06 +01:00
remote_thr Problem: can't build without libsodium from command line (MSVC) 2016-02-03 22:44:06 +01:00
libsodium.import.props Remove libsodium VS import props crypt32.lib dependency. 2014-07-22 12:01:15 -07:00
libsodium.import.xml Update VS build configurations. 2014-04-09 03:27:27 -07:00
libzmq.import.props Problem: can't build without libsodium from command line (MSVC) 2016-02-03 22:44:06 +01:00
libzmq.import.xml Problem: can't build without libsodium from command line (MSVC) 2016-02-03 22:44:06 +01:00
libzmq.sln Add executable projects to VS2013 solution. 2014-04-04 01:17:25 -07:00