base on An Eclipse Paho C client library for MQTT for Windows, Linux and MacOS. API documentation: https://eclipse-paho.github.io/paho.mqtt.c/ [](https://travis-ci.org/eclipse/paho.mqtt.c) [](https://lgtm.com/projects/g/eclipse/paho.mqtt.c/alerts/) [](https://scan.coverity.com/projects/paho-c) # Eclipse Paho C Client Library for the MQTT Protocol This repository contains the source code for the [Eclipse Paho](http://eclipse.org/paho) MQTT C client library. This code builds libraries which enable applications to connect to an [MQTT](http://mqtt.org) broker to publish messages, and to subscribe to topics and receive published messages. Synchronous and various asynchronous programming models are supported. ## Information About MQTT * [MQTT website](http://mqtt.org) * [The MQTT 3.1.1 standard](http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html) * [The MQTT 5.0 standard](https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html) * [HiveMQ introduction to MQTT](https://www.hivemq.com/mqtt/) * [OASIS Introduction to MQTT presentation](https://www.oasis-open.org/committees/download.php/49205/MQTT-OASIS-Webinar.pdf) ## Libraries The Paho C client comprises four variant libraries, shared or static: * paho-mqtt3a - asynchronous (MQTTAsync) * paho-mqtt3as - asynchronous with SSL/TLS (MQTTAsync) * paho-mqtt3c - "classic" / synchronous (MQTTClient) * paho-mqtt3cs - "classic" / synchronous with SSL/TLS (MQTTClient) [Which Paho C API to use, with some history, for context](https://modelbasedtesting.co.uk/2013/10/13/which-paho-mqtt-c-api-to-use-and-some-history/) ## Usage and API Detailed API documentation [is available online](https://eclipse-paho.github.io/paho.mqtt.c/MQTTClient/html/). It is also available by building the Doxygen docs in the ``doc`` directory. Samples are available in the Doxygen docs and also in `src/samples` for reference. These are: - *paho_c_pub.c* and *paho_c_sub.c:* command line utilities to publish and subscribe, -h will give help - *paho_cs_pub.c* and *paho_cs_sub.c:* command line utilities using MQTTClient to publish and subscribe - *MQTTClient_publish.c, MQTTClient_subscribe.c* and *MQTTClient_publish_async.c:* MQTTClient simple code examples - *MQTTAsync_publish.c* and *MQTTAsync_subscribe.c:* MQTTAsync simple code examples Some potentially useful blog posts: - [Paho client MQTT 5.0 support and command line utilities](https://modelbasedtesting.co.uk/2018/08/08/paho-c-client-mqtt-5-0-and-command-line-utilities/) - [MQTT, QoS and persistence](https://modelbasedtesting.co.uk/2013/11/24/mqtt-qos-and-persistence/) - [A story of MQTT 5.0](https://modelbasedtesting.co.uk/2018/04/09/a-story-of-mqtt-5-0/) [Various MQTT and MQTT-SN talks I've given.](https://modelbasedtesting.co.uk/talks-ive-given/) ## Runtime tracing A number of environment variables control runtime tracing of the C library. Tracing is switched on using `MQTT_C_CLIENT_TRACE` (a value of ON traces to stdout, any other value should specify a file to trace to). The verbosity of the output is controlled using the `MQTT_C_CLIENT_TRACE_LEVEL` environment variable - valid values are ERROR, PROTOCOL, MINIMUM, MEDIUM and MAXIMUM (from least to most verbose). The variable `MQTT_C_CLIENT_TRACE_MAX_LINES` limits the number of lines of trace that are output. ``` export MQTT_C_CLIENT_TRACE=ON export MQTT_C_CLIENT_TRACE_LEVEL=PROTOCOL ``` ## Reporting bugs Please open issues in the Github project: https://github.com/eclipse-paho/paho.mqtt.c/issues. ## More information Discussion of the Paho clients takes place on the [Eclipse paho-dev mailing list](https://dev.eclipse.org/mailman/listinfo/paho-dev). ## Follow Eclipse Paho on Twitter: [@eclipsepaho](https://twitter.com/eclipsepaho) General questions about the MQTT protocol are discussed in the [MQTT Google Group](https://groups.google.com/forum/?hl=en-US&fromgroups#!forum/mqtt). There is more information available via the [MQTT community site](http://mqtt.org). ## Building with CMake The build process currently supports a number of Linux "flavors" including ARM and s390, OS X, AIX and Solaris as well as the Windows operating system. The build process requires the following tools: * [CMake](http://cmake.org) * [GNU Make](https://www.gnu.org/software/make/) or [Ninja](https://martine.github.io/ninja/) * A conforming C compiler, such as [gcc](https://gcc.gnu.org/), [Clang](https://clang.llvm.org/), etc On Debian based systems this would mean that the following packages have to be installed: ``` $ apt-get install build-essential gcc make cmake cmake-gui cmake-curses-gui ``` Also, in order to build a debian package from the source code, the following packages have to be installed ``` $ apt-get install fakeroot devscripts dh-make lsb-release ``` Ninja can be downloaded from its github project page in the "releases" section. Optionally it is possible to build binaries with SSL/TLS support. This requires the OpenSSL libraries and includes to be available. E. g. on Debian: ``` $ apt-get install libssl-dev ``` The documentation requires doxygen and optionally graphviz: ``` $ apt-get install doxygen graphviz ``` ### Building your application with CMake If the Paho C library was built with CMake and is already installed on the system, it is relatively easy to set up a CMake build for your application. (If it's not already built and installed read the next section). The library can be built with several options which create variations of the library for asynchronous or synchronous use; encryption (SSL/TLS) support or not; and whether the library is shared or static. CMake exports all of the libraries that were built as targets, and the user can chose which is best suited for an application. The package is named: **eclipse-paho-mqtt-c** The namespace for all the targets is also: **eclipse-paho-mqtt-c** The target names are the same as the library names. The static libraries append *-static* to the target name even for platforms that use the same base name for shared and static libraries. So: Target|Description ------|----------- paho-mqtt3a | asynchronous, no encryption paho-mqtt3as | asynchronous with SSL/TLS support paho-mqtt3c | synchronous, no encryption paho-mqtt3cs | synchronous with SSL/TLS support paho-mqtt3a-static | asynchronous, no encryption, static linkage paho-mqtt3as-static | asynchronous with SSL/TLS support, static linkage paho-mqtt3c-static | synchronous, no encryption, static linkage paho-mqtt3cs-static | synchronous with SSL/TLS support, static linkage Remember, though, that not all of these targets may be available. It depends on how the library was built. A sample *CMakeLists.txt* for an application that uses the asynchronous library with encryption support *(paho-mqtt3as)* might look like this: ``` cmake_minimum_required(VERSION 3.5) project(MyMQTTApp VERSION 1.0.0 LANGUAGES C) find_package(eclipse-paho-mqtt-c REQUIRED) add_executable(MyMQTTApp MyMQTTApp.c) target_link_libraries(MQTTVersion eclipse-paho-mqtt-c::paho-mqtt3as) ``` If the library was installed to a non-traditional location, you may need to tell CMake where to find it using `CMAKE_PREFIX_PATH`. For example, if you installed it in */opt/mqtt/paho.mqtt.c* ``` $ cmake -DCMAKE_PREFIX_PATH=/opt/mqtt/paho.mqtt.c .. ``` ### Building the Paho C library with CMake Before compiling, determine the value of some variables in order to configure features, library locations, and other options: Variable | Default Value | Description ------------ | ------------- | ------------- PAHO_BUILD_SHARED | TRUE | Build a shared version of the libraries PAHO_BUILD_STATIC | FALSE | Build a static version of the libraries PAHO_HIGH_PERFORMANCE | FALSE | When set to true, the debugging aids internal tracing and heap tracking are not included. PAHO_WITH_SSL | FALSE | Flag that defines whether to build ssl-enabled binaries too. OPENSSL_ROOT_DIR | "" (system default) | Directory containing your OpenSSL installation (i.e. `/usr/local` when headers are in `/usr/local/include` and libraries are in `/usr/local/lib`) PAHO_BUILD_DOCUMENTATION | FALSE | Create and install the HTML based API documentation (requires Doxygen) PAHO_BUILD_SAMPLES | FALSE | Build sample programs PAHO_ENABLE_TESTING | TRUE | Build test and run MQTT_TEST_BROKER | tcp://localhost:1883 | MQTT connection URL for a broker to use during test execution MQTT_TEST_PROXY | tcp://localhost:1883 | Hostname of the test proxy to use MQTT_SSL_HOSTNAME | localhost | Hostname of a test SSL MQTT broker to use PAHO_BUILD_DEB_PACKAGE | FALSE | Build debian package Using these variables CMake can be used to generate your Ninja or Make files. Using CMake, building out-of-source is the default. Therefore it is recommended to invoke all build commands inside your chosen build directory but outside of the source tree. An example build session targeting the build platform could look like this: ``` $ mkdir /tmp/build.paho ; cd /tmp/build.paho $ cmake -DPAHO_WITH_SSL=TRUE -DPAHO_BUILD_DOCUMENTATION=TRUE \ -DPAHO_BUILD_SAMPLES=TRUE ~/paho.mqtt.c ``` Invoking cmake and specifying build options can also be performed using cmake-gui or ccmake (see https://cmake.org/runningcmake/). For example: ``` $ ccmake ~/paho.mqtt.c ``` To compile/link the binaries, to install, or to generate packages, use these commands: ``` $ cmake --build . $ cmake --build . --target install $ cmake --build . --target package ``` To build, install, or generate packages, you can also use the generated builder like _ninja_ or _make_ directly after invoking the initial CMake configuration step, such as `ninja package` or `make -j <number-of-jpbs> package`. ### Debug builds Debug builds can be performed by defining the value of the `CMAKE_BUILD_TYPE` option to `Debug`. For example: ``` $ cmake -DCMAKE_BUILD_TYPE=Debug ~/paho.mqtt.c ``` ### Running the tests Test code is available in the `test` directory. The tests can be built and executed with the CMake build system. The test execution requires a MQTT broker running. By default, the build system uses `localhost`, however it is possible to configure the build to use an external broker. These parameters are documented in the Build Requirements section above. After ensuring a MQTT broker is available, it is possible to execute the tests by starting the proxy and running `ctest` as described below: ``` $ python ../test/mqttsas.py & $ ctest -VV ``` ### Cross compilation Cross compilation using CMake is performed by using so called "toolchain files" (see: http://www.vtk.org/Wiki/CMake_Cross_Compiling). The path to the toolchain file can be specified by using CMake's `-DCMAKE_TOOLCHAIN_FILE` option. In case no toolchain file is specified, the build is performed for the native build platform. For your convenience toolchain files for the following platforms can be found in the `cmake` directory of Eclipse Paho: * Linux x86 * Linux ARM11 (a.k.a. the Raspberry Pi) * Windows x86_64 * Windows x86 The provided toolchain files assume that required compilers/linkers are to be found in the environment, i. e. the PATH-Variable of your user or system. If you prefer, you can also specify the absolute location of your compilers in the toolchain files. Example invocation for the Raspberry Pi: ``` $ cmake -GNinja -DPAHO_WITH_SSL=TRUE -DPAHO_BUILD_SAMPLES=TRUE \ -DPAHO_BUILD_DOCUMENTATION=TRUE \ -DOPENSSL_LIB_SEARCH_PATH=/tmp/libssl-dev/usr/lib/arm-linux-gnueabihf \ -DOPENSSL_INC_SEARCH_PATH="/tmp/libssl-dev/usr/include/openssl;/tmp/libssl-dev/usr/include/arm-linux-gnueabihf" \ -DCMAKE_TOOLCHAIN_FILE=~/paho.mqtt.c/cmake/toolchain.linux-arm11.cmake \ ~/paho.mqtt.c ``` Compilers for the Raspberry Pi and other ARM targets can be obtained from ARM (https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/downloads) This example assumes that OpenSSL-libraries and includes have been installed in the `/tmp/libssl-dev` directory. Example invocation for Windows 64 bit: ``` $ cmake -DPAHO_BUILD_SAMPLES=TRUE \ -DCMAKE_TOOLCHAIN_FILE=~/paho.mqtt.c/cmake/toolchain.win64.cmake \ ~/paho.mqtt.c ``` In this case the libraries and executable are not linked against OpenSSL Libraries. Cross compilers for the Windows platform can be installed on Debian like systems like this: ``` $ apt-get install gcc-mingw-w64-x86-64 gcc-mingw-w64-i686 ``` ## Build instructions for GNU Make Ensure the OpenSSL development package is installed. Then from the client library base directory run: ``` $ make $ sudo make install ``` This will build and install the libraries. To uninstall: ``` $ sudo make uninstall ``` To build the documentation requires doxygen and optionally graphviz. ``` $ make html ``` The provided GNU Makefile is intended to perform all build steps in the ```build``` directory within the source-tree of Eclipse Paho. Generated binares, libraries, and the documentation can be found in the ```build/output``` directory after completion. Options that are passed to the compiler/linker can be specified by typical Unix build variables: Variable | Description ------------ | ------------- CC | Path to the C compiler CFLAGS | Flags passed to compiler calls LDFLAGS | Flags passed to linker calls ## Building paho-mqtt - Using vcpkg You can download and install paho-mqtt using the [vcpkg](https://github.com/Microsoft/vcpkg) dependency manager: git clone https://github.com/Microsoft/vcpkg.git cd vcpkg ./bootstrap-vcpkg.sh ./vcpkg integrate install ./vcpkg install paho-mqtt The paho-mqtt port in vcpkg is kept up to date by Microsoft team members and community contributors. If the version is out of date, please [create an issue or pull request](https://github.com/Microsoft/vcpkg) on the vcpkg repository. ## Fully static builds with musl libc (By Frank Pagliughi) [musl libc](https://musl.libc.org/) is is an implementation of the C standard library built on top of the Linux system call API, including interfaces defined in the base language standard, POSIX, and widely agreed-upon extensions. Users of the Rust library, which wraps this one, had been complaining that they could not compile using the musl build tools. Musl is a small std C lib that can be statically linked. With the latest Paho C library (and a very minor tweak to the build), we're now able to build Rust apps using musl and Paho C that are fully static; no runtime dependencies on the platform; not even on the standard C lib. $ ./async_publish Publishing a message on the 'test' topic $ ldd async_publish not a dynamic executable So, for example, if maintaining a suite of apps for some newer and older embedded Linux boards, the same executables could be deployed without worry about the C ABI on the particular boards. Certainly C apps using the Paho library could do this also. ## Microsoft Windows ### Calling convention As is normal for C programs on Windows, the calling convention is __cdecl. See the Microsoft documentation here: https://docs.microsoft.com/en-us/cpp/cpp/cdecl?view=vs-2019 If you call this library from another language, you may need to take this into account. ", Assign "at most 3 tags" to the expected json: {"id":"4778","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"