esp-idf/examples/protocols/esp_http_client/main/CMakeLists.txt

# Embed the server root certificate into the final binary
#
# (If this was a component, we would set COMPONENT_EMBED_TXTFILES here.)
set(requires esp-tls nvs_flash esp_event esp_netif esp_http_client)
idf_build_get_property(target IDF_TARGET)

if(${target} STREQUAL "linux")
    list(APPEND requires esp_stubs protocol_examples_common)
endif()
idf_component_register(SRCS "esp_http_client_example.c"
                    INCLUDE_DIRS "."
                    PRIV_REQUIRES ${requires}
                    EMBED_TXTFILES howsmyssl_com_root_cert.pem
                    postman_root_cert.pem)
cmake: make main a component again 2018-09-11 09:44:12 +08:00			`# Embed the server root certificate into the final binary`
			`#`
			`# (If this was a component, we would set COMPONENT_EMBED_TXTFILES here.)`
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			`set(requires esp-tls nvs_flash esp_event esp_netif esp_http_client)`
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)`

			`if(${target} STREQUAL "linux")`
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			`list(APPEND requires esp_stubs protocol_examples_common)`
Update esp_http_client example to build for linux target 2022-11-08 16:31:52 +05:30			`endif()`
examples: use new component registration api 2019-04-28 15:38:46 +08:00			`idf_component_register(SRCS "esp_http_client_example.c"`
			`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 ${requires}`
Fix esp_http_client example: Set proper server verification by adding the postman root cert for https_async demo test case. 2021-04-04 12:51:20 +05:30			`EMBED_TXTFILES howsmyssl_com_root_cert.pem`
			`postman_root_cert.pem)`