[LLVMbugs] [Bug 17284] New: Set -fmsc-version in Visual Studio Platform Tools files

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=17284

            Bug ID: 17284
           Summary: Set -fmsc-version in Visual Studio Platform Tools
                    files
           Product: new-bugs
           Version: trunk
          Hardware: PC
                OS: other
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: new bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: p_hampson at wargaming.net
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

Created attachment 11235
  --> http://llvm.org/bugs/attachment.cgi?id=11235&action=edit
Set -fmsc-version in MSBuild 4.0 PlatformTools integration files

When using clang-cl through the MSBuild integrations, it seems reasonable that
you'd want -fmsc-version to match the version you're pretending to be, and are
using the platform headers for.

So here's a patch (built upon attachment 11212 from bug 17259, but only
trivially) which adds the appropriate -fmsc-version parameter to the
command-line given to cl.exe.

This resolved a problem for me where the Windows SDK 7.1A used by
LLVM-vs2012_xp (bug 17259) was picking up the wrong definitions from the VC11
headers, and failing to compile due to undefined SAL annotation macros.

-- 
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/20130919/6462ef74/attachment.html>