Skip to content
ZeroMQ core engine in C++, implements ZMTP/3.0
C++ C CMake Shell Python Batchfile Makefile
Find file
Latest commit 18dcc32 @c-rack c-rack Merge pull request #1803 from bluca/ci_default_only_on_secondary
Problem: too many CI builds
Failed to load latest commit information.
builds Problem: tests don't build on Windows
doc Problem: test_large_msg kills my system temporarily
include Problem: test_large_msg kills my system temporarily
packaging Problem: deprecated `zmq_utils.h` is still included
perf Merge pull request #1764 from GreatFruitOmsk/master
src Problem: tcp_address.cpp has messy include usage
tests Problem: tests don't build on Windows
tools Problem: copyright year is still 2015
.gitignore Merge pull request #1798 from hintjens/master
.hgeol Line-ending conversion rules for hg-git users and enabled use of .git…
.mailmap Fix mailmap entry for Max Skaller
.travis.yml Problem: too many CI builds
AUTHORS Problem: tweetnacl sources are a mess
CMakeLists.txt Merge pull request #1799 from hintjens/master
COPYING missing COPYING file added
COPYING.LESSER Added note about tivotisation
Dockerfile Add Docker support
FindSodium.cmake CMake: use libsodium if available, else use tweet_nacl
INSTALL Added autogen.sh hint
MAINTAINERS Fixed email addresses in the MAITAINERS file
Makefile.am Merge pull request #1799 from hintjens/master
NEWS Updated development master to 4.2.x
README.cygwin.md Implement a definitive cygwin target for libzmq.
README.md Problem: libzmq appveyor build status is not visible
acinclude.m4 Problem: some configure options are confusing
appveyor.yml Problem: Windows CI fails due to libsodium build failure
autogen.sh Check for libtoolize instead of libtool on Linux
branding.bmp Add ZeroMQ branding.
ci_build.sh Problem: CI use of sodium or nacl is confusing
configure.ac Problem: typo in configure.ac, can't use libsodium
installer.ico Add ZeroMQ branding.
version.sh m4_esyscmd_s doesnt seem to be portable across different systems

README.md

ZeroMQ

Build Status Build status

Welcome

The ZeroMQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. ZeroMQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.

Building and installation

See the INSTALL file included with the distribution.

Resources

Extensive documentation is provided with the distribution. Refer to doc/zmq.html, or "man zmq" after you have installed libzmq on your system.

Website: http://www.zeromq.org/

Development mailing list: zeromq-dev@lists.zeromq.org Announcements mailing list: zeromq-announce@lists.zeromq.org

Git repository: http://github.com/zeromq/libzmq

ZeroMQ developers can also be found on the IRC channel #zeromq, on the Freenode network (irc.freenode.net).

License

The project license is specified in COPYING and COPYING.LESSER.

libzmq is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License (LGPL) as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.

As a special exception, the Contributors give you permission to link this library with independent modules to produce an executable, regardless of the license terms of these independent modules, and to copy and distribute the resulting executable under terms of your choice, provided that you also meet, for each linked independent module, the terms and conditions of the license of that module. An independent module is a module which is not derived from or based on this library. If you modify this library, you must extend this exception to your version of the library.

libzmq is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.

Something went wrong with that request. Please try again.