components/bootloader/subproject/main/CMakeLists.txt

idf_component_register(SRCS "bootloader_start.c"
                    REQUIRES bootloader bootloader_support)

idf_build_get_property(scripts BOOTLOADER_LINKER_SCRIPT)
target_linker_script(${COMPONENT_LIB} INTERFACE "${scripts}")

target_link_libraries(${COMPONENT_LIB} INTERFACE "-u bootloader_hooks_include")
make bootloader_support support esp32s2beta 2019-05-27 14:29:43 +08:00			`idf_component_register(SRCS "bootloader_start.c"`
			`REQUIRES bootloader bootloader_support)`
components: update with build system changes 2019-05-10 10:53:08 +08:00
fix(bootloader): add a new property that contains the default linker scripts 2024-12-16 17:35:34 +08:00			`idf_build_get_property(scripts BOOTLOADER_LINKER_SCRIPT)`
Merge branch 'master' into feature/esp32s2beta_update 2019-08-08 13:44:24 +10:00			`target_linker_script(${COMPONENT_LIB} INTERFACE "${scripts}")`
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
			`target_link_libraries(${COMPONENT_LIB} INTERFACE "-u bootloader_hooks_include")`