-
Notifications
You must be signed in to change notification settings - Fork 107
Config
If you define MQTT_USE_TLS macro, mqtt_cpp enables TLS features. In order to use TLS features, you need to prepare OpenSSL.
If you define MQTT_NO_TLS macro, mqtt_cpp disables TLS features. So you don't need to prepare OpenSSL.
If you define MQTT_USE_WS macro, mqtt_cpp supports WebSocket using Beast.
Update: Since the Boost Libraries version 1.66.0, it contains the Beast.
If you define MQTT_USE_STR_CHECK, mqtt_cpp checks UTF8 string validation at the place MQTT spec required.
If you define MQTT_USE_LOG, then mqtt_cpp outputs log messages using Boost.Log.
If you define MQTT_STD_OPTIONAL macro, mqtt_cpp use std::optional
instead of boost::optional
.
If you define MQTT_STD_VARIANT macro, mqtt_cpp use std::variant
instead of boost::variant
.
If you define MQTT_STD_STRING_VIEW macro, mqtt_cpp use std::string_view
instead of boost::string_view
.
Note: If you don't define MQTT_STD_STRING_VIEW and Boost version is less than 1.61.0, then boost::string_ref
is used.
If you define MQTT_NS macro with a string, the string is used as the namespace of mqtt_cpp. If you don't define it, then mqtt
is used as the namespace of mqtt_cpp.
mqtt_cpp outputs warning message if you use deprecated functions.
If you define MQTT_USE_DEPRECATED, then warning message is suppressed.
Note that deprecated functions will be removed in the future release. So I recommend that use MQTT_USE_DEPRECATED as temporary.
If set it to ON (default), then build examples.
If set it to ON (default), then build tests.
- Requirements
- Config
- Tutorial
- Authentication and Authorization
- Advanced topics
- Examples
- API Reference
- Versioning Policy
- How to contribute