Mirrors/libwebsockets
1
0
Fork 0
mirror of https://github.com/warmcat/libwebsockets.git synced 2025-03-16 00:00:07 +01:00
Code Issues Releases Wiki Activity
libwebsockets/minimal-examples/embedded/esp32/esp-wrover-kit/CMakeLists.txt

34 lines
988 B
Text
Raw Normal View History

esp32: shift to support latest esp-idf Esp-idf has an improved but still kind of abused cmake- based build system now. If we see ESP_PLATFORM coming as a cmake var, we can know we are being built from inside the esp-idf config system. Leave the existing esp32 arrangements alone but triggered off ESP_PLATFORM, adapt to use the cross toolchain file and various quirks automatically. In this way you can build lws a part of your project in a much cleaner way. Prepare a minimal esp32 test app for use in Sai Adapt .sai.json to build for esp32
2020-05-14 21:28:48 +01:00
cmake_minimum_required(VERSION 3.5)
if (ESP_PLATFORM)
include($ENV{IDF_PATH}/tools/cmake/project.cmake)
cmake: mark all the subprojects as explicitly C We don't need a C++ compiler but if we don't spell it out, cmake assumes it C + C++ compiler needed.
2020-08-19 17:37:42 +01:00
project(lws-minimal-esp32 C)
esp32: shift to support latest esp-idf Esp-idf has an improved but still kind of abused cmake- based build system now. If we see ESP_PLATFORM coming as a cmake var, we can know we are being built from inside the esp-idf config system. Leave the existing esp32 arrangements alone but triggered off ESP_PLATFORM, adapt to use the cross toolchain file and various quirks automatically. In this way you can build lws a part of your project in a much cleaner way. Prepare a minimal esp32 test app for use in Sai Adapt .sai.json to build for esp32
2020-05-14 21:28:48 +01:00
enable_testing()
target_link_libraries(lws-minimal-esp32.elf websockets)
drivers: initial generic gpio and i2c plus bitbang Make a start on generic peripheral and bus drivers to provide meta-functionality regardless of platform. On the one hand this simply provides... - bitbang i2c on top of esp-idf gpio apis - ssd1306 oled chip driver as found on Heltec WB32 - modifications to the minimal example test for esp32 to use that ... on the other hand, those capabilities are provided by creating: - an abstract i2c class object - an abstract gpio class object - i2c class implementation using the abstract gpio for bitbang - an abstract display class object - an abstract display state (brightness, animated change, on/off/init tracking, autodim after inactive, auto-off / blanking after inactive) ... with the intention, eg, you only have to add a platform implementation for the gpio to be able to use the i2c-based display drivers and state handling, and i2c bitbang, without any other modifications.
2020-06-10 19:17:08 +01:00
option(LWS_WITH_DRIVERS "With generic drivers for gpio, i2c, display etc" ON)
set(LWS_WITH_DRIVERS ON)
lws_netdev
2020-06-22 20:05:06 +01:00
option(LWS_WITH_SECURE_STREAMS "With secure streams" ON)
set(LWS_WITH_SECURE_STREAMS ON)
option(LWS_WITH_LWSAC "With lwsac" ON)
set(LWS_WITH_LWSAC ON)
lws_netdev: use lws_settings Perform the AP selection using lws_settings and a generic scan state machine
2020-07-02 15:38:53 +01:00
option(LWS_WITH_STRUCT_JSON "With lws_struct JSON" ON)
set(LWS_WITH_STRUCT_JSON ON)
lws_netdev
2020-06-22 20:05:06 +01:00
option(LWS_WITH_SYS_NTPCLIENT "With ntpclient" ON)
set(LWS_WITH_SYS_NTPCLIENT ON)
drivers: initial generic gpio and i2c plus bitbang Make a start on generic peripheral and bus drivers to provide meta-functionality regardless of platform. On the one hand this simply provides... - bitbang i2c on top of esp-idf gpio apis - ssd1306 oled chip driver as found on Heltec WB32 - modifications to the minimal example test for esp32 to use that ... on the other hand, those capabilities are provided by creating: - an abstract i2c class object - an abstract gpio class object - i2c class implementation using the abstract gpio for bitbang - an abstract display class object - an abstract display state (brightness, animated change, on/off/init tracking, autodim after inactive, auto-off / blanking after inactive) ... with the intention, eg, you only have to add a platform implementation for the gpio to be able to use the i2c-based display drivers and state handling, and i2c bitbang, without any other modifications.
2020-06-10 19:17:08 +01:00
esp32: shift to support latest esp-idf Esp-idf has an improved but still kind of abused cmake- based build system now. If we see ESP_PLATFORM coming as a cmake var, we can know we are being built from inside the esp-idf config system. Leave the existing esp32 arrangements alone but triggered off ESP_PLATFORM, adapt to use the cross toolchain file and various quirks automatically. In this way you can build lws a part of your project in a much cleaner way. Prepare a minimal esp32 test app for use in Sai Adapt .sai.json to build for esp32
2020-05-14 21:28:48 +01:00
add_subdirectory(libwebsockets)
add_test(NAME flashing COMMAND idf.py flash)
set_tests_properties(flashing PROPERTIES
WORKING_DIRECTORY ${CMAKE_SOURCE_DIR}
TIMEOUT 120)
add_test(NAME boot COMMAND /usr/local/bin/sai-expect)
set_tests_properties(boot PROPERTIES
DEPENDS flashing
esp32: ctest: increase timeout for linkup and test to 60s
2020-07-14 18:17:30 +01:00
TIMEOUT 60)
esp32: shift to support latest esp-idf Esp-idf has an improved but still kind of abused cmake- based build system now. If we see ESP_PLATFORM coming as a cmake var, we can know we are being built from inside the esp-idf config system. Leave the existing esp32 arrangements alone but triggered off ESP_PLATFORM, adapt to use the cross toolchain file and various quirks automatically. In this way you can build lws a part of your project in a much cleaner way. Prepare a minimal esp32 test app for use in Sai Adapt .sai.json to build for esp32
2020-05-14 21:28:48 +01:00
endif()
Reference in a new issue Copy permalink