Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
CMake
CMake
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,225
    • Issues 3,225
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 13
    • Merge Requests 13
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • External Wiki
    • External Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CMake
  • CMakeCMake
  • Merge Requests
  • !3024

Merged
Opened Feb 26, 2019 by Brad King@brad.kingOwner

VS: Fix detection of clang-cl with -T llvm

  • Overview 3
  • Commits 1
  • Pipelines 1
  • Changes 1

When using a VS generator with -T llvm, MSBuild relies on the "LLVM Compiler Toolchain" VS Extension. This does not put clang-cl in the PATH inside the build, and LLVM no longer provides a cl replacement either. Therefore we need another way to extract the path to the CMAKE_{C,CXX}_COMPILER. Fortunately the LLVM VS integration provides a $(ClangClExecutable) macro we can reference to get the path.

Fixes: #18983 (closed)

Assignee
Assign to
Reviewer
Request review from
3.14.0
Milestone
3.14.0 (Past due)
Assign milestone
Time tracking
Reference: cmake/cmake!3024
Source branch: vs-llvm-extension