[llvm-branch-commits] [clang] [lldb] release/22.x: build: adjust LLDB and clang library naming on Windows (#185084) (PR #197493)

[Charles Zablit via llvm-branch-commits]

charles-zablit wrote:

> > > From my reading of the bug, it seems this can easily be worked around by renaming the produced binary? Is that not the case?
> > 
> > 
> > It can be worked around that way yes. Wouldn't this still count as a build failure when building lldb, even if there is a manual workaround for it?
> 
> That's true. When did it start failing? Or has it always failed in this way?

I assume it's been this way for a while. The lldb build bots use MSVC instead of clang, just like the release builds. This could have only been caught by a maintainer trying to build with clang, or an end user trying to build from source using clang (which is how we found this issue in the first place).

https://github.com/llvm/llvm-project/pull/197493