esp-idf/examples/custom_bootloader/bootloader_hooks/CMakeLists.txt

# For more information about build system see
# https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/build-system.html
# The following five lines of boilerplate have to be in your project's
# CMakeLists in this exact order for cmake to work correctly
cmake_minimum_required(VERSION 3.5)

include($ENV{IDF_PATH}/tools/cmake/project.cmake)
project(main)
bootloader: override the 2nd stage bootloader Add the possibility to have user bootloader components. This is performed from an application/project, by creating bootloader components. To do so, it is required to create a `bootloader_component` directory containing the custom modules to be compiled with the bootloader. Thanks to this, two solutions are available to override the bootloader now: - Using hooks within a user bootloader component - Using a user defined `main` bootloader component to totally override the old implementation Please check the two new examples in `examples/custom_bootloader` * Closes https://github.com/espressif/esp-idf/issues/7043 2021-04-15 10:31:33 +08:00			`# For more information about build system see`
			`# https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/build-system.html`
			`# The following five lines of boilerplate have to be in your project's`
			`# CMakeLists in this exact order for cmake to work correctly`
			`cmake_minimum_required(VERSION 3.5)`

			`include($ENV{IDF_PATH}/tools/cmake/project.cmake)`
			`project(main)`