michaelh/zephyr

Fork 0

Commit graph

Author	SHA1	Message	Date
Torsten Rasmussen	d7862cf776	cmake: using ${ZEPHYR_BASE} instead of $ENV{ZEPHYR_BASE} With the introduction of ZephyrConfig.cmake all parts of CMake code should rely on the CMake ZEPHYR_BASE variable instead of the environment setting. This ensures that after the first CMake invocation, then all subsequent invocation in same build folder will use same zephyr base. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>	2020-03-27 16:23:46 +01:00
Mark Ruvald Pedersen	197197a579	cmake: Toolchain abstraction: Introduce toolchain_ld_configure_files No functional change expected. This is motivated by the wish to abstract Zephyr's usage of toolchains, permitting non-intrusive porting to other (commercial) toolchains. Signed-off-by: Mark Ruvald Pedersen <mped@oticon.com>	2019-05-12 12:50:57 -04:00

Author

SHA1

Message

Date

Torsten Rasmussen

d7862cf776

cmake: using ${ZEPHYR_BASE} instead of $ENV{ZEPHYR_BASE}

With the introduction of ZephyrConfig.cmake all parts of CMake code
should rely on the CMake ZEPHYR_BASE variable instead of the environment
setting.

This ensures that after the first CMake invocation, then all subsequent
invocation in same build folder will use same zephyr base.

Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>

2020-03-27 16:23:46 +01:00

Mark Ruvald Pedersen

197197a579

cmake: Toolchain abstraction: Introduce toolchain_ld_configure_files

No functional change expected.

This is motivated by the wish to abstract Zephyr's usage of toolchains,
permitting non-intrusive porting to other (commercial) toolchains.

Signed-off-by: Mark Ruvald Pedersen <mped@oticon.com>

2019-05-12 12:50:57 -04:00

2 commits