build: Fix usage of hardcoded zephyr.{elf,bin,hex}
Its possible to rename the executable we build via the Kconfig symbol CONFIG_KERNEL_BIN_NAME. So we really should use ${KERNEL_ELF_NAME}, ${KERNEL_BIN_NAME} and ${KERNEL_HEX_NAME} variables instead of hardcoded zephyr.elf, zephyr.bin, and zephyr.elf. This fixes an build issue with tests/misc/test_build/buildsystem.kconfig.utf8_in_values on up_squared_adsp and lpcxpresso11u68 platforms. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
This commit is contained in:
parent
7eb8cf2515
commit
d2b0735c12
8 changed files with 9 additions and 9 deletions
|
@ -19,7 +19,7 @@ add_custom_target(
|
|||
DEPENDS base_module
|
||||
DEPENDS ${ZEPHYR_FINAL_EXECUTABLE}
|
||||
COMMAND ${CMAKE_OBJCOPY} --dump-section .data=mod-apl.bin $<TARGET_FILE:base_module>
|
||||
COMMAND ${CMAKE_OBJCOPY} --add-section .module=mod-apl.bin --set-section-flags .module=load,readonly ${CMAKE_BINARY_DIR}/zephyr/zephyr.elf ${CMAKE_BINARY_DIR}/zephyr/zephyr.elf.mod
|
||||
COMMAND ${CMAKE_OBJCOPY} --add-section .module=mod-apl.bin --set-section-flags .module=load,readonly ${CMAKE_BINARY_DIR}/zephyr/${KERNEL_ELF_NAME} ${CMAKE_BINARY_DIR}/zephyr/${KERNEL_ELF_NAME}.mod
|
||||
)
|
||||
|
||||
add_custom_target(
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue