diff options
| author | Hafiz Abid Qadeer <abidh@codesourcery.com> | 2020-12-07 09:09:59 +0000 |
|---|---|---|
| committer | Hafiz Abid Qadeer <abidh@codesourcery.com> | 2020-12-07 09:19:52 +0000 |
| commit | 275592e714130345a481a5cb889c89b73a98614f (patch) | |
| tree | 3c9824e10a7ad96a63779cb0c448237f30836561 /lldb/test/Shell/ScriptInterpreter/Python | |
| parent | 7d04e70627aa0734ce820bec0dcb7fa28a9ea457 (diff) | |
| download | llvm-275592e714130345a481a5cb889c89b73a98614f.zip llvm-275592e714130345a481a5cb889c89b73a98614f.tar.gz llvm-275592e714130345a481a5cb889c89b73a98614f.tar.bz2 | |
Provide default location of sysroot for Baremetal toolchain.
Currently, Baremetal toolchain requires user to pass a sysroot location
using a --sysroot flag. This is not very convenient for the user. It also
creates problem for toolchain vendors who don't have a fixed location to
put the sysroot bits.
Clang does provide 'DEFAULT_SYSROOT' which can be used by the toolchain
builder to provide the default location. But it does not work if toolchain
is targeting multiple targets e.g. arm-none-eabi/riscv64-unknown-elf which
clang is capable of doing.
This patch tries to solve this problem by providing a default location of
the toolchain if user does not explicitly provides --sysroot. The exact
location and name can be different but it should fulfill these conditions:
1. The sysroot path should have a target triple element so that multi-target
toolchain problem (as I described above) could be addressed.
2. The location should not be $TOP/$Triple as this is used by gcc generally
and will be a problem for installing both gcc and clang based toolchain at
the same location.
Reviewed By: jroelofs
Differential Revision: https://reviews.llvm.org/D92677
Diffstat (limited to 'lldb/test/Shell/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions
