[all-commits] [llvm/llvm-project] a26ec5: [clang-scan-deps] Infer the tool locations from PA...

Martin Storsjö via All-commits all-commits at lists.llvm.org
Fri Sep 13 13:18:32 PDT 2024


  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: a26ec542371652e1d774696e90016fd5b0b1c191
      https://github.com/llvm/llvm-project/commit/a26ec542371652e1d774696e90016fd5b0b1c191
  Author: Martin Storsjö <martin at martin.st>
  Date:   2024-09-13 (Fri, 13 Sep 2024)

  Changed paths:
    M clang/include/clang/Tooling/CompilationDatabase.h
    M clang/lib/Tooling/CMakeLists.txt
    A clang/lib/Tooling/LocateToolCompilationDatabase.cpp
    M clang/test/ClangScanDeps/modules-extern-submodule.c
    M clang/test/ClangScanDeps/modules-full-output-tu-order.c
    M clang/test/ClangScanDeps/modules-has-include-umbrella-header.c
    M clang/test/ClangScanDeps/modules-header-sharing.m
    M clang/test/ClangScanDeps/modules-implementation-module-map.c
    M clang/test/ClangScanDeps/modules-implementation-private.m
    M clang/test/ClangScanDeps/modules-priv-fw-from-pub.m
    A clang/test/ClangScanDeps/resolve-executable-path.c
    M clang/tools/clang-scan-deps/ClangScanDeps.cpp

  Log Message:
  -----------
  [clang-scan-deps] Infer the tool locations from PATH (#108539)

This allows the clang driver to know which tool is meant to be executed,
which allows the clang driver to load the right clang config files, and
allows clang to find colocated sysroots.

This makes sure that doing `clang-scan-deps -- <tool> ...` looks up
things in the same way as if one just would execute `<tool> ...`, when
`<tool>` isn't an absolute or relative path.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications


More information about the All-commits mailing list