eebf8c78db
Upgrade to release 1.5.3: - Fix the bundled Paho C build foc C23 compilers by forcing C99 compliance in CMake build - Code base updated to to C++17 - Now a C++17 compiler is required to compile the library - CMake minimum required version raised to v3.13 - Need a fairly recent CMake for C++17 support (>= v3.12) - CMake v3.13 allows INSTALL(TARGETS) to work outside the current directory. - Clients always created for v5 persistence format, making it universal for any connection. - If the application specifies a version it is kept as a hint for default connections. - The version for the connection should be specified in the connect options. - The create_options now have all the parameters to create a client. - Can specify Server URL, Client ID, and persistence in the create options. - New client constructor that takes just the options object - The client caches a const create_options struct with all the creation parameters - Client creation internally simplified without breaking the public API - Expanded the message constmer to be a full client "event" consumer. - The events are for connected, connection_lost, disconnected, message arrived, and application shutdown. - The application can get client state change notifications without resorting to callbacks. - There's a new persistence_type (std::variant) that can hold any of the persistence specifiers (none, file directory, or user interface). - Most of the class static constants are now constexpr. - Removed the fake ReasonCode::MQTTPP_V3_CODE. Now all reason codes in a v3 connection are SUCCESS. - The mqtt::exception checks if the 'rc' return code actually contains a reason code error, amd if so, sets it as the reason code. - property can now report the typeid of its contained value. - The properties list implements a const iterator - Added a to_string() and operator<<() for reason codes. - thread_queue is now closable. - Added documentation for UNIX domain sockets coming in with Paho C v1.3.14 - Removed the manual implementation of make_unique<>() - Added create_options assignment operators. - Fixed some corner cases for topic_filter::matches() - Cleaned up and fixed a number of example apps. - Most apps now except a server URI from the command line - 'data_publish' example uses C++17 std::filesystem for creating a file-based encrypted persistence for messages. - Updated local CI (buildtst.sh) for current compilers and unit tests. - Reorganized the source repository - Completely reformat the sources and added a .clang-format file (a project master and a slightly-different one for headers). Signed-off-by: Leon Anavi <leon.anavi@konsulko.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
meta-oe
This layer depends on:
URI: git://github.com/openembedded/openembedded-core.git branch: master
luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below
pacman -S lib32-gcc-libs lib32-glibc
Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'
You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.
Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.
Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.
layer maintainer: Khem Raj raj.khem@gmail.com