6a42ede43b
Some toolchains may generate convoluted paths when reporting accessory tools. This is the case with GCC in the Zephyr SDK toolchain. For example, for a Zephyr SDK installed under `C:\Portable\Zephyr` a call to `gcc --print-prog-name=ld.bfd` should normally return something like `c:/portable/zephyr/zephyr-sdk-0.16.5/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd.exe` but because of how the toolchain was created the path reported gets all messed up with relative fragments. In above case, the actual path reported was `c:/portable/zephyr/zephyr-sdk-0.16.5/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe` One might argue that this should be fixed in the toolchain which could be possible for the Zephyr SDK but not for other toolchains (definitely not for proprietary ones). Signed-off-by: Nicolas Lebedenco <nicolas@lebedenco.net> |
||
|---|---|---|
| .. | ||
| app | ||
| bintools | ||
| compiler | ||
| emu | ||
| flash | ||
| ide | ||
| linker | ||
| linker_script | ||
| makefile_exports | ||
| modules | ||
| reports | ||
| sca | ||
| toolchain | ||
| usage | ||
| util | ||
| cfb.cmake | ||
| extra_flags.cmake | ||
| gcc-m-cpu.cmake | ||
| gcc-m-fpu.cmake | ||
| gen_version_h.cmake | ||
| hex.cmake | ||
| kobj.cmake | ||
| mcuboot.cmake | ||
| package_helper.cmake | ||
| pristine.cmake | ||
| target_toolchain_flags.cmake | ||
| verify-toolchain.cmake | ||
| vif.cmake | ||