Richard Allen 1fb02a9a60 fix(websocket): fix esp_event dependency management
Move esp_event from PRIV_REQUIRES to REQUIRES, as it is
included by esp_websocket_client.h, so any code including
that header also requires esp_event.

This resolves the following build error for files not
explicitly requiring esp_event:

ninja: build stopped: subcommand failed.
Compilation failed because esp_websocket_client.h (in "espressif__esp_websocket_client" component) includes esp_event.h, provided by esp_event component(s).
However, esp_event component(s) is in the private requirements list of "espressif__esp_websocket_client".
To fix this, move esp_event from PRIV_REQUIRES into REQUIRES list of idf_component_register call in ...\managed_components\espressif__esp_websocket_client\CMakeLists.txt.
ninja failed with exit code 1, output of the command is in...
2024-03-08 10:10:48 -06:00
2023-03-31 12:04:46 +04:00

Collection of protocol components for ESP-IDF

How to use

The ESP-Protocols repository contains a collection of protocol components for ESP-IDF. Additionally, each component is available in IDF Component Registry. Please refer to instructions in ESP-IDF

Components

esp_modem

mDNS

esp_websocket_client

ASIO port

esp_mqtt_cxx

console_simple_init

console_cmd_ping

console_cmd_ifconfig

console_cmd_wifi

Description
Collection of ESP-IDF components related to networking protocols
Readme 42 MiB
Languages
C 56.7%
C++ 35.3%
Python 4.4%
CMake 2.4%
Shell 0.7%
Other 0.5%