Keith Burzinski c0ad5d1d16 Initial attempt at supporting ESP-IDF 5.0.0 (#4364) ... * requirements: add pyparsing >= 3.0 ESP-IDF >= 5.0 requires pyparsing's rest_of_file, which was introduced in version 3.0. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> * esp32: fix build with ESP-IDF >= 5 We need to include esp_timer.h to be able to use esp_timer_get_time(). This header existed in ESP-IDF < 5 so we don't need if guards. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> * ota: fix build with ESP-IDF >= 5 As of version 5, esp_task_wdt_init() takes a struct as argument. We also need to include spi_flash_mmap.h. [split unrelated change into separate commits, maintain ESP-IDF < 5 compat, use esp_task_wdt_reconfigure, add commit message] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> * core: fix build with ESP-IDF >= 5 These header files already existed in ESP-IDF < 5 so skip if guards. [add commit message] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> * wifi: fix build with ESP-IDF >= 5 ESP-IDF 4.1 introduced the esp-netif API as successor to the tcp_adapter API. The tcp_adapter API was removed in ESP-IDF 5.0.0. Part of the wifi component was already migrated to the new API. Migrate the leftover uses of the old API to the new API to fix build on ESP-IDF >= 5. The version of ESP-IDF currently in use (4.4.4) supports the new API, so we don't need any if guards to maintain backwards compatibility. Also replace xQueueHandle, which is a pre FreeRTOS v8.0.0 data type, with QueueHandle_t, so we don't need to enable backward compatibility (CONFIG_FREERTOS_ENABLE_BACKWARD_COMPATIBILITY). This reverts part of commit d42f35de5d to wifi_component_esp_idf.cpp, as the esp-netif API handles that internally. [replace pre FreeRTOS v8.0.0 data type, add commit message] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> * mdns: fix build with ESP-IDF >= 5 In ESP-IDF 5.0.0, the mdns component was removed and moved to another repository. Since the mdns component in esphome is always built, we need to add the mdns component from the esp-protocols repository. This component depends on ESP-IDF >= 5.0, so we need to add a version guard. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> * docker: install python3-venv As of version 6.0.1, platform-espressif32 requires python3-venv. Switching between esp-idf 4.4.4 and 5.0 causes problems with esp-idf python dependencies installed by PlatformIO. They've solved this by using venv. Install python3-venv so that platform-espressif32 6.0.1 and later can be used, and we don't need to wipe the dependencies manually when switching esp-idf versions. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> --------- Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> Co-authored-by: Stijn Tintel <stijn@linux-ipv6.be>		2023-04-20 03:54:06 +00:00
..
ha-addon-rootfs/etc	Add Home Assistant integration discovery (#4328)	2023-01-26 17:48:04 +01:00
build.py	Format docker/build.py (#4313)	2023-01-19 12:04:51 +13:00
docker_entrypoint.sh	Fix docker pio settings not applied (#2370)	2021-09-22 10:32:39 +02:00
Dockerfile	Initial attempt at supporting ESP-IDF 5.0.0 (#4364)	2023-04-20 03:54:06 +00:00
generate_tags.py	Move from docker manifest command to buildx with platforms (#4320)	2023-01-20 14:01:29 +13:00
platformio_install_deps.py	Fix platformio_install_deps no longer installing all lib_deps (#2584)	2021-10-21 15:29:32 +02:00