[llvm-bugs] [Bug 37187] New: VisualStudio projects always out of date using clang-cl toolset integration

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=37187

            Bug ID: 37187
           Summary: VisualStudio projects always out of date using
                    clang-cl toolset integration
           Product: new-bugs
           Version: 6.0
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P
         Component: new bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: bherrera at reification.io
                CC: llvm-bugs at lists.llvm.org

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
<ItemDefinitionGroup>
  <ClCompile>
    ...
    <!-- clang-cl embeds debug data in obj files. does not generate pdb per
lib. if option not cleared projects will always appear out of date to MSVS. -->
    <ProgramDataBaseFileName/> 
  </ClCompile>
</ItemDefinitionGroup>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20180420/84d59841/attachment.html>