[Clang][Driver] Fix the missing Target-Triple-Level include path resolution in Baremetal Driver (#165321)

The current baremetal driver implementation does not have a way to
derive the target-triple-level include path within the sysroot.

This feature is especially useful in setups where header paths deviate
from the default bare-metal assumptions. For example, when headers are
shared across target triples, it becomes necessary to organise them
under target-triple-specific directories to ensure correct resolution..

GitOrigin-RevId: e4169e7bc10f743761d00a1a1642fdfe2d853969
4 files changed
tree: b024e212aeeae18359435b216b594b5d5b78ac90
  1. bindings/
  2. cmake/
  3. docs/
  4. examples/
  5. include/
  6. lib/
  7. runtime/
  8. test/
  9. tools/
  10. unittests/
  11. utils/
  12. www/
  13. .clang-format
  14. .clang-tidy
  15. .gitignore
  16. AreaTeamMembers.txt
  17. CMakeLists.txt
  18. INSTALL.txt
  19. LICENSE.TXT
  20. Maintainers.rst
  21. NOTES.txt
  22. README.md
README.md

C language Family Front-end

Welcome to Clang.

This is a compiler front-end for the C family of languages (C, C++ and Objective-C) which is built as part of the LLVM compiler infrastructure project.

Unlike many other compiler frontends, Clang is useful for a number of things beyond just compiling code: we intend for Clang to be host to a number of different source-level tools. One example of this is the Clang Static Analyzer.

If you're interested in more (including how to build Clang) it is best to read the relevant websites. Here are some pointers: