mirror of
https://github.com/zeromq/libzmq.git
synced 2024-12-13 10:52:56 +01:00
7c3a420be4
Solution: Implement the current same kind of mechanism as CZMQ & ZYRE, with enhancement. Enhancement: When required and if LIBSODIUM is not set, the build tool checks for an already existing clone, close to LIBZMQ. This mechanism is close to what is done by LIBZMQ/CZMQ/ZYRE for their dependencies. Additionnaly: Do not copy current source tree to any 'cache' folder. Use current folder, but make sure all is cleaned before compilation is launched. This is a lot safer, when building different clones in parrallel... Enhancement to be reported to CZMQ/ZYRE via ZProject. |
||
---|---|---|
.. | ||
abi-compliance-checker | ||
android | ||
cmake | ||
coverage | ||
cygwin | ||
deprecated-msvc | ||
fuzz | ||
gyp | ||
ios | ||
mingw32 | ||
nuget | ||
openwrt | ||
qnx | ||
valgrind | ||
vxworks | ||
zos | ||
Makefile.am | ||
README |
This directory holds build tools, i.e. tools we use to build the current code tree. Packaging tools (which take released tarballs or github code repos) should go into /packaging. Note: 'deprecated-msvc' contains deprecated prepared Visual Studio Solution files for various Visual Studio versions. These are no longer maintained, and may or may not work. Please use cmake instead to build with Visual Studio. Rationale: The solution and project files are hard to maintain, since there are different variants for each Visual Studio version. The tests have never been included there for this reason, so they were never usable for actual development of libzmq. If you encounter that something that worked before does not work with CMake, please open as issue at https://github.com/zeromq/libzmq/issues.