Open llvmbot opened 6 years ago
Re-discovered and posted about here: http://lists.llvm.org/pipermail/llvm-dev/2019-January/129589.html
This is the same problem discussed in llvm/llvm-project#35488 #c6
The workaround of setting an empty ProgramDataBaseFileName
is new though.
Does the new VS integration (did we land it yet?) fix this?
Latest 7.0 snapshot does not appear to have 2017 integration
Does the new VS integration (did we land it yet?) fix this?
Extended Description
Issue observed using LLVM 6.0 x64 toolchain (
<llvm_insall_dir>/msbuild-bin/cl.exe
) with Visual Studio 14 (and Visual Studio 15 using a manual toolset integration),MSVS default compiler options include flag for specifying location of
.pdb
file for libraries. clang-cl silently ignores this switch and embeds intermediate debug data in obj files instead of producing a single separate pdb for the entire library. (not an issue - debugging works fine)Projects always appear out of date due to msbuild expecting a pdb file and not finding one.
This can be remedied by modifying the
toolset-vs20XX.props
file used for MSVS/MSBuild integration:Under the compile options add a tag to clear the pdb filename option