Sebastian Bøe c05a931bce cmake: Explicitly set the entry point when testing toolchain flags ... We are observing warnings when test-compiling toolchain flags that look like: cannot find entry symbol _start; defaulting to 00000000000010d4 To fix this warning we explicitly set an entry point to an arbitrary address. The files are only compiled, not run, so the entry point does not need to be correct. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>		2019-09-19 09:29:57 -05:00
..
app	cmake: add new search locations for shield overlay and conf files	2019-09-12 07:17:49 -05:00
backports
bintools
compiler	cmake: Explicitly set the entry point when testing toolchain flags	2019-09-19 09:29:57 -05:00
emu	boards/x86: add Intel64 (64-bit long-mode) QEMU target board	2019-09-15 11:33:47 +08:00
flash
ide
linker/ld
reports
toolchain	cmake: check sdk_version format	2019-09-19 08:16:19 -04:00
usage
util
boards.cmake
ccache.cmake
cfb.cmake
dts.cmake	kconfig: Add new functions to kconfigfunctions to use EDT	2019-09-13 11:42:34 -05:00
extensions.cmake	cmake: Fix bug where -Wno- flags could not be compatbility-checked	2019-09-07 23:32:55 +02:00
extra_flags.cmake
gcc-m-cpu.cmake
generic_toolchain.cmake
git.cmake
hex.cmake
host-tools.cmake
kconfig.cmake	kconfig: support multiple DTS bindings directories	2019-09-16 05:29:27 -05:00
kobj.cmake
pristine.cmake
python.cmake
target_toolchain.cmake
version.cmake
zephyr_module.cmake