Hmm... That is strange, but CMake does never stop puzzling me (; Could
you please compress your whole output folder, upload it somewhere and
post a link to the file here? I assume you are using distortos 0.7.0,
but what version of the toolchain do you have installed? Could you also
share the exact commands you executed to configure the build folder?
Try to build with `ninja -v distortosTest`, this will show you the
exact commands that were executed. If possible, do `ninja clean`, then
`ninja -v distortosTest` and post the log in here.
If my suspicion is correct, maybe you first had the output folder
configured one way (possibly a completely wrong configuration?), then
tried to reconfigure it (without deleting it) to a different board? I'm
not sure this is possible at all, but maybe it is. In cases like this
the only solution is to delete the build folder entirely and start from
scratch. Even if change of the most basic CMake options (like the
change of toolchain file) is technically possible in a configured tree,
any such attempt will produce a configuration which is broken beyond
repair. Try with a new build folder and see whether it helps.
Note that CMake tries to use /usr/bin/objcopy, while it should be using
arm-none-eabi-objcopy. CMAKE_OBJCOPY is not set explicitly by
distortos, however in here (as well as the CI server and several other
PCs I tried) it is properly detected to have the same triple as the
compilers. If it doesn't work on your side with a clean build folder,
than maybe it should actually be set explicitly... In this case you
could try setting that manually via cmake-gui - just add a new entry
CMAKE_OBJCOPY with the value "<path-to-the-toolchain>/bin/arm-none-
eabi-objcopy" (quite possible that you will have to do the same thing
for OBJDUMP or some other tools). Or modify the toolchain file to set
this variable(s) and see whether it helps (note that after any change
to toolchain file you should completely delete the build folder and
start from scratch!).
Let me know what you'll find out!