generic-library/libzmq
1
0
Fork 0
mirror of https://github.com/zeromq/libzmq.git synced 2024-12-12 10:33:52 +01:00
Code Issues Projects Releases Wiki Activity
0a1aa1e4a7
libzmq/builds/deprecated-msvc
History
Luca Boccassi ff47aeb791 Problem: no permission to relicense tweetnacl integration 
Solution: remove implementation. Frank Hartmann <soundart@gmx.net>,
the author, rejected our request to relicense under MPL2, so we
have to remove his copyrighted work.
Tweetnacl is not security-supported and could not be used in
production environments anyway, the supported backend is libsodium.
2023-06-04 23:54:31 +01:00
..
build Problem: prepared Visual Studio solution files are hard to maintain and redundant with CMake builds 2018-05-23 17:26:28 +02:00
properties Problem: prepared Visual Studio solution files are hard to maintain and redundant with CMake builds 2018-05-23 17:26:28 +02:00
vs2008 Problem: prepared Visual Studio solution files are hard to maintain and redundant with CMake builds 2018-05-23 17:26:28 +02:00
vs2010 Problem: no permission to relicense tweetnacl integration 2023-06-04 23:54:31 +01:00
vs2012 Problem: no permission to relicense tweetnacl integration 2023-06-04 23:54:31 +01:00
vs2013 Problem: no permission to relicense tweetnacl integration 2023-06-04 23:54:31 +01:00
vs2015 Problem: no permission to relicense tweetnacl integration 2023-06-04 23:54:31 +01:00
vs2015_xp Fix typos 2022-02-11 00:45:06 +02:00
vs2017 Problem: no permission to relicense tweetnacl integration 2023-06-04 23:54:31 +01:00
.gitignore Problem: prepared Visual Studio solution files are hard to maintain and redundant with CMake builds 2018-05-23 17:26:28 +02:00
errno.cpp Problem: prepared Visual Studio solution files are hard to maintain and redundant with CMake builds 2018-05-23 17:26:28 +02:00
errno.hpp Problem: prepared Visual Studio solution files are hard to maintain and redundant with CMake builds 2018-05-23 17:26:28 +02:00
Makefile.am Problem: prepared Visual Studio solution files are hard to maintain and redundant with CMake builds 2018-05-23 17:26:28 +02:00
platform.hpp Problem: prepared Visual Studio solution files are hard to maintain and redundant with CMake builds 2018-05-23 17:26:28 +02:00
readme.txt Problem: prepared Visual Studio solution files are hard to maintain and redundant with CMake builds 2018-05-23 17:26:28 +02:00
resource.h Problem: prepared Visual Studio solution files are hard to maintain and redundant with CMake builds 2018-05-23 17:26:28 +02:00
resource.rc Problem: prepared Visual Studio solution files are hard to maintain and redundant with CMake builds 2018-05-23 17:26:28 +02:00

readme.txt 

For building on Windows, use:

     cd build
     ./build.bat

This requires that the CMD.EXE be created using the DevStudio Tools link to create a CMD.EXE window. Also, make sure that the name of the project folder is libzmq (not e.g. libzmq-master) as this is required for correct linking.

Visual Studio product and C++ compiler Versions:

Visual C++ 2008 => Visual C++ 9
Visual C++ 2010 => Visual C++ 10
Visual C++ 2012 => Visual C++ 11
Visual C++ 2013 => Visual C++ 12
Visual C++ 2015 => Visual C++ 14
Visual C++ 2017 => Visual C++ 15

Note that solution file icons reflect the compiler version ([9], [10], [11], [12], [14], [15]), not the product version.

The vs2017/vs2015/vs2013/vs2012/vs2010 solution and project files differ only in versioning.

More info here:

http://en.wikipedia.org/wiki/Visual_C%2B%2B

If multiple DevStudio versions are installed, you can run build.bat in separate windows each created by the desired DevStudio target.

To build for all versions of Visual Studio (excluding vs2008), you can run buildall.bat. This is generally a maintainer task.