<html>
<head>
<base href="http://llvm.org/bugs/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Set -fmsc-version in Visual Studio Platform Tools files"
href="http://llvm.org/bugs/show_bug.cgi?id=17284">17284</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Set -fmsc-version in Visual Studio Platform Tools files
</td>
</tr>
<tr>
<th>Product</th>
<td>new-bugs
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>new bugs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>p_hampson@wargaming.net
</td>
</tr>
<tr>
<th>CC</th>
<td>llvmbugs@cs.uiuc.edu
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=11235" name="attach_11235" title="Set -fmsc-version in MSBuild 4.0 PlatformTools integration files">attachment 11235</a> <a href="attachment.cgi?id=11235&action=edit" title="Set -fmsc-version in MSBuild 4.0 PlatformTools integration files">[details]</a></span>
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 <span class=""><a href="attachment.cgi?id=11212" name="attach_11212" title="Patch to add LLVM-vs2012_xp toolset to MSBuild integration">attachment 11212</a> <a href="attachment.cgi?id=11212&action=edit" title="Patch to add LLVM-vs2012_xp toolset to MSBuild integration">[details]</a></span> from <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Support Visual Studio 2012 targeting Windows XP with v110_xp toolset work-alike"
href="show_bug.cgi?id=17259">bug 17259</a>, 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 (<a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Support Visual Studio 2012 targeting Windows XP with v110_xp toolset work-alike"
href="show_bug.cgi?id=17259">bug 17259</a>) was picking up the wrong definitions from the VC11
headers, and failing to compile due to undefined SAL annotation macros.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>