zephyr/cmake
Torsten Rasmussen eb2a705497 cmake: support absolute path in zephyr_code_relocate() function
Fixes: #27288

The Zephyr CMake function `zephyr_code_relocate()` would treat any file
argument as relative to `CMAKE_CURRENT_SOURCE_DIR` even if an absolute
path is provided.

A file with absolute path would thus become
`${CMAKE_CURRENT_SOURCE_DIR}/<absolute-path>/<file>` which leads to a
non existing file.

This is fixed by checking if path argument is a relative path, and only
use `CMAKE_CURRENT_SOURCE_DIR` in such case.

Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2020-09-10 16:24:45 -05:00
..
app cmake: ensure consistent behavior between x_ROOT settings 2020-09-10 21:30:24 +02:00
bintools
compiler cmake: c++ compiler flag exclusion, -Werror=implicit-int 2020-09-07 17:22:37 +02:00
emu
flash
ide
linker cmake: MWDT linker command list fix. 2020-09-05 10:22:56 -05:00
makefile_exports cmake: export build flags to external build systems excluding SHELL tag 2020-09-10 11:31:53 +02:00
reports
toolchain
usage
util
boards.cmake
ccache.cmake
cfb.cmake
dts.cmake cmake: ensure consistent behavior between x_ROOT settings 2020-09-10 21:30:24 +02:00
extensions.cmake cmake: support absolute path in zephyr_code_relocate() function 2020-09-10 16:24:45 -05:00
extra_flags.cmake
gcc-m-cpu.cmake
generic_toolchain.cmake cmake: Ignore LDFLAGS and AFLAGS from environment 2020-09-10 15:35:50 -05:00
git.cmake
hex.cmake
host-tools.cmake
kconfig.cmake cmake: ensure consistent behavior between x_ROOT settings 2020-09-10 21:30:24 +02:00
kobj.cmake
mcuboot.cmake
pristine.cmake
python.cmake
target_toolchain_flags.cmake
target_toolchain.cmake
version.cmake
west.cmake
zephyr_module.cmake