<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 - Make lld-link not depend on mt.exe on Windows"
href="https://bugs.llvm.org/show_bug.cgi?id=38966">38966</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Make lld-link not depend on mt.exe on Windows
</td>
</tr>
<tr>
<th>Product</th>
<td>lld
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</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>COFF
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>nicolasweber@gmx.de
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>On non-Windows, we use libxml2 and llvm/lib/WindowsManifest/ to merge
manifests.
On Windows, libxml2 usually doesn't exist, so we rely on mt.exe being on PATH.
The way forward is probably to use msxml on Windows instead of libxml2, since
that's always around. I have prototyped this a bit at
<a href="https://reviews.llvm.org/D42910">https://reviews.llvm.org/D42910</a> but it's incomplete.
Once this is done, lld-link.exe no longer relies on PATH and the only env var
it relies on is LIB, which can be passed via /libpath:. So once this is done,
no special env needs to be set to be able to run lld-link -- once we have this,
we can stop running lld-link.exe under `ninja -t msvc` in the chrome/win build
on win hosts. (We already don't need it on non-win hosts.)</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>