<html>
<head>
<base href="https://bugs.llvm.org/">
</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 - Documentation on recommended workflows"
href="https://bugs.llvm.org/show_bug.cgi?id=39408">39408</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Documentation on recommended workflows
</td>
</tr>
<tr>
<th>Product</th>
<td>Documentation
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Windows NT
</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>General docs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>llvm-dev@redking.me.uk
</td>
</tr>
<tr>
<th>CC</th>
<td>greg.bedwell@sony.com, llvm-bugs@lists.llvm.org, zturner@google.com
</td>
</tr></table>
<p>
<div>
<pre>On the llvm-dev discussion about supporting building with Visual Studio:
<a href="https://lists.llvm.org/pipermail/llvm-dev/2018-October/126778.html">https://lists.llvm.org/pipermail/llvm-dev/2018-October/126778.html</a>
Zachary suggested alternate VS/VSCode + Ninja workflows, but we don't do much
to document these:
<a href="https://llvm.org/docs/GettingStarted.html">https://llvm.org/docs/GettingStarted.html</a>
<a href="https://clang.llvm.org/get_started.html">https://clang.llvm.org/get_started.html</a>
We have "Using Ninja alongside Visual Studio" but it doesn't explain the exact
procedures involved, especially for day2day development, debugging etc. Nor do
we mention the builtin VS CMake support etc.
It'd be really good if we could document such workflows better (VS/VSCode,
Ninja etc.) so that they are more obvious/attractive to developers.</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>