package zmq-lwt

  1. Overview
  2. Docs
Lwt aware bindings to zmq

Install 

dune-project
 Dependency

github.com Readme Changelog MIT License Edit opam file Versions (11)

Authors

  1. A
    Anders Fugmann <anders@fugmann.net>

Maintainers

  1. A
    Anders Fugmann <anders@fugmann.net>

Sources

zmq-5.1.3.tbz
sha256=24b32de3829a103e548f37e00f7e03fca72a00e1b67d6ee6d3d75fbae31b8806
sha512=7b4c1e7bce06d7f340603c7d56ffc1714c5a0601040d72bbe5591e3ae5cf24e7835b5da7bd525c19632db45059544ddcdeecd507298e993b7b761a764c1d8ff7

Description

Added to opam-repository:

README

OCaml bindings for ZMQ 4.x

Build Status

Dependencies

  • OPAM
  • OCaml >= 4.03.0, OCaml >= 4.04.1 for zmq-async
  • Async >= v0.11.0 for zmq-async
  • Lwt for zmq-lwt
  • libzmq (c lib) >= 4.x

Install

opam install zmq

Uninstall

opam remove zmq

Documentation

API documentation can be found here

Development

With OPAM 2.x you can create a local switch which will install all dependencies automatically.

opam switch create ./ 4.06
make

License

See LICENSE.md.

Thanks

To the guys from the #ocaml channel, gildor, thelema, kaustuv and many others, wagerlabs, little-arhat and the ocaml-uint authors.

Dependencies (4)

  1. lwt < "5.7.0"
  2. dune
  3. zmq = version
  4. ocaml >= "4.03.0"

Dev Dependencies (1)

  1. ounit2 with-test

Used by (2)

  1. jupyter
  2. jupyter-kernel >= "0.7"

Conflicts

None

Build status

Results of building zmq-lwt with each compiler on check.ci.ocaml.org, run of against opam-repository 7cdc698. All results for this package.

Each result links to its build log. To keep crawlers from overloading the site, build logs require a GitHub sign-in (see ocurrent/opam-health-check). On your first log, GitHub asks you to “Authorize opam-health-check”, the OCurrent app that runs these checks; it sees only your public profile, not your repositories. The sign-in lasts 30 days.

This version is not in the latest run; the versions below are.

Version OCaml 4.11 OCaml 4.14 OCaml 5.2 OCaml 5.4 OCaml 5.5
6.0.0 good good good good good
  • good Package successfully built
  • partial One of the dependencies failed to build
  • bad Package failed to build
  • n/a Package is not available in this environment
  • internal Internal failure