OVMS3-idf/components/esp_system/CMakeLists.txt

idf_component_register(SRCS "panic.c" "system_api.c" "startup.c"
                    INCLUDE_DIRS include
                    PRIV_INCLUDE_DIRS private_include
                    PRIV_REQUIRES spi_flash app_update
                                  # requirements due to startup code
                                  nvs_flash pthread app_trace
                    LDFRAGMENTS "linker.lf")

add_subdirectory(port)

# After system initialization, `start_app` (and its other cores variant) is called. 
# This is provided by the user or from another component. Since we can't establish 
# dependency on what we don't know, force linker to not drop the symbol regardless
# of link line order.
target_link_libraries(${COMPONENT_LIB} INTERFACE "-u start_app")

if (NOT CONFIG_ESP_SYSTEM_SINGLE_CORE_MODE)
    target_link_libraries(${COMPONENT_LIB} INTERFACE "-u start_app_other_cores")
endif()
esp32, esp32s2: move startup code into esp_system 2020-03-03 04:22:41 +00:00			`idf_component_register(SRCS "panic.c" "system_api.c" "startup.c"`
esp32, esp32s2: move panic handling code to new component 2020-02-02 15:23:16 +00:00			`INCLUDE_DIRS include`
			`PRIV_INCLUDE_DIRS private_include`
esp_system: startup flow modifications Changes the startup flow to the ff: hardware -> core libraries init -> other libraries init -> os init (optional) -> app_main - hardware init resides in the port layer, and is the entry point - core libraries init executes init functions of core components - other libraries init executes init functions of other components (weak references) - after other lib is init, the app_main function is called, however, an OS can wrap the real call to app_main to init its own stuff, and then call the real app_main 2020-02-05 14:40:15 +00:00			`PRIV_REQUIRES spi_flash app_update`
esp_system: fix various review issues 2020-06-09 00:17:48 +00:00			`# requirements due to startup code`
			`nvs_flash pthread app_trace`
esp32, esp32s2: move panic handling code to new component 2020-02-02 15:23:16 +00:00			`LDFRAGMENTS "linker.lf")`

			`add_subdirectory(port)`
esp32, esp32s2: move startup code into esp_system 2020-03-03 04:22:41 +00:00
esp_system: introduce intermediary function to call after system init This MR uses an intermediary function `start_app` to call after system initialization instead of `app_main`. In RTOS builds, freertos provides `start_app` and calls `app_main`. In non-RTOS builds, user provides `start_app` directly. 2020-06-10 13:13:31 +00:00			# After system initialization, `start_app` (and its other cores variant) is called.
			`# This is provided by the user or from another component. Since we can't establish`
			`# dependency on what we don't know, force linker to not drop the symbol regardless`
			`# of link line order.`
			`target_link_libraries(${COMPONENT_LIB} INTERFACE "-u start_app")`
esp_system: introduce single core mode proxy config 2020-02-13 12:43:23 +00:00
			`if (NOT CONFIG_ESP_SYSTEM_SINGLE_CORE_MODE)`
esp_system: introduce intermediary function to call after system init This MR uses an intermediary function `start_app` to call after system initialization instead of `app_main`. In RTOS builds, freertos provides `start_app` and calls `app_main`. In non-RTOS builds, user provides `start_app` directly. 2020-06-10 13:13:31 +00:00			`target_link_libraries(${COMPONENT_LIB} INTERFACE "-u start_app_other_cores")`
esp_system: introduce single core mode proxy config 2020-02-13 12:43:23 +00:00			`endif()`