examples/protocols/sockets/tcp_client/main/CMakeLists.txt

idf_build_get_property(target IDF_TARGET)

if("${CONFIG_EXAMPLE_IPV4}" STREQUAL y)
    set(tcp_client_ip tcp_client_v4.c)
else()
    set(tcp_client_ip tcp_client_v6.c)
endif()

idf_component_register(SRCS "tcp_client_main.c" "${tcp_client_ip}"
                                INCLUDE_DIRS "."
                                PRIV_REQUIRES unity nvs_flash esp_netif)
fix: Fix protocols example to build without setting target Protocol examples used to raise an error if the target was not set and `idf.py build` command was used. This commit fix this error and when IDF_TARGET is not set, ESP32 is selected as default target 2023-09-20 14:05:10 +05:30			`idf_build_get_property(target IDF_TARGET)`

tcp_client example: support for Linux target. 2022-07-23 00:01:50 +05:30			`if("${CONFIG_EXAMPLE_IPV4}" STREQUAL y)`
			`set(tcp_client_ip tcp_client_v4.c)`
			`else()`
			`set(tcp_client_ip tcp_client_v6.c)`
			`endif()`

			`idf_component_register(SRCS "tcp_client_main.c" "${tcp_client_ip}"`
			`INCLUDE_DIRS "."`
change(examples): explicitly specify component dependencies for examples Currently, several examples do not explicitly state their component dependencies, relying instead on the default behavior that includes all registered components and commonly required ones in the build. Explicitly adding component dependencies can reduce build time when set(COMPONENTS main) is used. Signed-off-by: Frantisek Hrbata <frantisek.hrbata@espressif.com> 2024-09-24 14:22:10 +02:00			`PRIV_REQUIRES unity nvs_flash esp_netif)`