[zeromq-dev] cppzmq revival and RFC on design goals and supported platforms

Simon.Giesecke at btc-ag.com Simon.Giesecke at btc-ag.com
Thu May 24 16:26:22 CEST 2018


Hi Tomer,

did you use the current master version? 

Building cppzmq with cmakeworks with a non-cmake-built libzmq as well, this is also tested in the CI. As you can see in the CMakeList.txt file, it prefers a libzmq cmake package, but falls back to pkg-config if that is not found: https://github.com/zeromq/cppzmq/blob/1f14f9a34e23281bb88ed7e59ebd85c48542fa39/CMakeLists.txt#L9

If this doesn't work for you, please provide details of your setup, so we can resolve this.

This applies if you want to consume cppzmq as cmake package, otherwise you can simply use the header files as Luca already suggested.

Best regards
Simon

Von: zeromq-dev [mailto:zeromq-dev-bounces at lists.zeromq.org] Im Auftrag von Tomer Eliyahu
Gesendet: Donnerstag, 24. Mai 2018 13:40
An: ZeroMQ development list <zeromq-dev at lists.zeromq.org>
Betreff: Re: [zeromq-dev] cppzmq revival and RFC on design goals and supported platforms

I suggest to add support for building cppzmq without enforcing the build of libzmq via cmake. In openwrt for example, there is cmake support but zmq is built with autotools, which majes integrating cppzmq cumbersome so we eventually had to patch cppzmq to a previous version and strip some cmake features which were recently added. 

On Wed, May 23, 2018, 19:07 <mailto:Simon.Giesecke at btc-ag.com> wrote:
Hi,

Pawel Kurdybacha (kurdybacha) and me (sigiesec) have recently started to "revive" cppzmq (https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fzeromq%2Fcppzmq&data=02%7C01%7Csimon.giesecke%40btc-ag.com%7Cc0b516f851204eb3b25108d5c16b2999%7Cc064efb078954eebb406a40bc377bc7d%7C0%7C0%7C636627588467547581&sdata=m62lXDj0U2uNMQkJN8gKn%2FARhJx5o%2Fl7%2BFO72FSP35A%3D&reserved=0), the light-weight C++ wrapper around libzmq. We added CI for Windows/MSVC, Linux and MacOS, implemented tests, cleaned up the CMake infrastructure, formatted the source code consistently and added some overview documentation.

If you are using cppzmq or are interested in using it, we encourage you to have a look at the recent changes.

One particular point we would like to seek feedback on are the design goals, which have recently been documented for the first time. I tried to extrapolate them from the actual design, and from the reasons we chose to use cppzmq in comparison to other alternatives. These are part of the https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fzeromq%2Fcppzmq%2Fblob%2Fmaster%2FREADME.md&data=02%7C01%7Csimon.giesecke%40btc-ag.com%7Cc0b516f851204eb3b25108d5c16b2999%7Cc064efb078954eebb406a40bc377bc7d%7C0%7C0%7C636627588467547581&sdata=yQdG7mnHVVTgL0F8PGYUPl5%2BIObGn1X%2BLSXA0DKfQRQ%3D&reserved=0 file:

* cppzmq maps the libzmq C API to C++ concepts. In particular:
   * it is type-safe (the libzmq C API exposes various class-like concepts as void*)
   * it provides exception-based error handling (the libzmq C API provides errno-based error handling)
   * it provides RAII-style classes that automate resource management (the libzmq C API requires the user to take care to free resources explicitly)
* cppzmq is a light-weight, header-only binding. You only need to include the header file zmq.hpp (and maybe zmq_addon.hpp) to use it.
* zmq.hpp is meant to contain direct mappings of the abstractions provided by the libzmq C API, while zmq_addon.hpp provides additional higher-level abstractions.

We would like to here from you if you agree with these design goals. If you have any opposing views, proposals for improvement or extension of the design goals, please share them on the mailing list or by sending a PR.

Another part of the README is a section on the supported platforms. Please review this section, in particular if you do not use MacOS, Linux or Windows/MSVC with a recent compiler. If you successfully use a different platform, please send a PR to include this in the list of "Additional platforms that are known to work". Support for non-C++11 compilers is already partial only, and might be removed completely, unless there are users that still require such support.

Of course, you are also invited to contribute extensions, new features, cleanup, further tests, etc. to cppzmq.

Best regards
Simon

--
i.A. Simon Giesecke
BTC Business Technology Consulting AG
Kurfürstendamm 33
10719 Berlin
E-Mail: mailto:Simon.Giesecke at btc-ag.com

Rechtliche Hinweise: 
http://www.btc-ag.com/impressum.htm
Handelsregister: Amtsgericht Oldenburg HRB 4717
Aufsichtsratsvorsitzender: Michael Heidkamp
Vorstand: Dr. Jörg Ritter, Dirk Thole

_______________________________________________
zeromq-dev mailing list
mailto:zeromq-dev at lists.zeromq.org
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.zeromq.org%2Fmailman%2Flistinfo%2Fzeromq-dev&data=02%7C01%7Csimon.giesecke%40btc-ag.com%7Cc0b516f851204eb3b25108d5c16b2999%7Cc064efb078954eebb406a40bc377bc7d%7C0%7C0%7C636627588467547581&sdata=%2BFngG0DTABbjDLt0Q8PGHo2sIcJndoH7db5OyJpDCGk%3D&reserved=0


More information about the zeromq-dev mailing list