8c363321db
Issue is that when users creates a custom bootloader from $IDF_PATH/components/bootloader. Parent project build uses the copy but bootloader subproject build uses the original still. The issue is solved by passing the custom bootloader as extra component directory so bootloader build knows to use the new copy (itself) in the build.
74 lines
2.9 KiB
CMake
74 lines
2.9 KiB
CMake
# This is for tracking the top level project path
|
|
if(BOOTLOADER_BUILD)
|
|
set(main_project_path "${CMAKE_BINARY_DIR}/../..")
|
|
else()
|
|
set(main_project_path "${IDF_PROJECT_PATH}")
|
|
endif()
|
|
|
|
get_filename_component(secure_boot_signing_key
|
|
"${CONFIG_SECURE_BOOT_SIGNING_KEY}"
|
|
ABSOLUTE BASE_DIR "${main_project_path}")
|
|
if(NOT EXISTS ${secure_boot_signing_key})
|
|
# If the signing key is not found, create a phony gen_secure_boot_signing_key target that
|
|
# fails the build. fail_at_build_time also touches CMakeCache.txt to cause a cmake run next time
|
|
# (to pick up a new signing key if one exists, etc.)
|
|
fail_at_build_time(gen_secure_boot_signing_key
|
|
"Secure Boot Signing Key ${CONFIG_SECURE_BOOT_SIGNING_KEY} does not exist. Generate using:"
|
|
"\tespsecure.py generate_signing_key ${CONFIG_SECURE_BOOT_SIGNING_KEY}")
|
|
else()
|
|
add_custom_target(gen_secure_boot_signing_key)
|
|
endif()
|
|
|
|
if(BOOTLOADER_BUILD OR NOT IDF_BUILD_ARTIFACTS)
|
|
return() # don't keep recursing, generate on project builds
|
|
endif()
|
|
|
|
# Glue to build the bootloader subproject binary as an external
|
|
# cmake project under this one
|
|
#
|
|
#
|
|
set(bootloader_build_dir "${IDF_BUILD_ARTIFACTS_DIR}/bootloader")
|
|
set(bootloader_binary_files
|
|
"${bootloader_build_dir}/bootloader.elf"
|
|
"${bootloader_build_dir}/bootloader.bin"
|
|
"${bootloader_build_dir}/bootloader.map"
|
|
)
|
|
|
|
# These additional files may get generated
|
|
if(CONFIG_SECURE_BOOTLOADER_REFLASHABLE)
|
|
set(bootloader_binary_files
|
|
${bootloader_binary_files}
|
|
"${bootloader_build_dir}/bootloader-reflash-digest.bin"
|
|
"${bootloader_build_dir}/secure-bootloader-key-192.bin"
|
|
"${bootloader_build_dir}/secure-bootloader-key-256.bin"
|
|
)
|
|
endif()
|
|
|
|
if((NOT CONFIG_SECURE_BOOT_ENABLED) OR
|
|
CONFIG_SECURE_BOOTLOADER_REFLASHABLE OR
|
|
CONFIG_SECURE_BOOTLOADER_ONE_TIME_FLASH)
|
|
externalproject_add(bootloader
|
|
# TODO: support overriding the bootloader in COMPONENT_PATHS
|
|
SOURCE_DIR "${CMAKE_CURRENT_LIST_DIR}/subproject"
|
|
BINARY_DIR "${bootloader_build_dir}"
|
|
CMAKE_ARGS -DSDKCONFIG=${SDKCONFIG} -DIDF_PATH=${IDF_PATH}
|
|
-DSECURE_BOOT_SIGNING_KEY=${secure_boot_signing_key}
|
|
-DEXTRA_COMPONENT_DIRS=${CMAKE_CURRENT_LIST_DIR}
|
|
INSTALL_COMMAND ""
|
|
BUILD_ALWAYS 1 # no easy way around this...
|
|
BUILD_BYPRODUCTS ${bootloader_binary_files}
|
|
DEPENDS gen_secure_boot_signing_key
|
|
)
|
|
else()
|
|
fail_at_build_time(bootloader "Invalid bootloader target: bad sdkconfig?")
|
|
endif()
|
|
|
|
# this is a hack due to an (annoying) shortcoming in cmake, it can't
|
|
# extend the 'clean' target to the external project
|
|
# see thread: https://cmake.org/pipermail/cmake/2016-December/064660.html
|
|
#
|
|
# So for now we just have the top-level build remove the final build products...
|
|
set_property(DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}" APPEND PROPERTY
|
|
ADDITIONAL_MAKE_CLEAN_FILES
|
|
${bootloader_binary_files})
|