<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 - Need clang-config tool"
href="https://bugs.llvm.org/show_bug.cgi?id=32080">32080</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Need clang-config tool
</td>
</tr>
<tr>
<th>Product</th>
<td>clang
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</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>unassignedclangbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>scott+llvm+bugzilla@pakin.org
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>Could you please have the Clang build process install a clang-config utility
that works similarly to llvm-config?
llvm-config is extremely convenient for determining the set of headers and
libraries to use when building LLVM-related code (e.g., an LLVM compiler pass).
In particular, it makes it possible for users without convenient access to an
LLVM source tree to build third-party programs that are not distributed with
LLVM and need only the LLVM headers and libraries to compile and link.
In contrast, a Clang tool I'm currently developing requires the following
grotesque link line:
-lclangFrontend -lclangTooling -lclangBasic -lclangSerialization
-lclangSema -lLLVMSupport -lLLVMMC -lLLVMCore -lclangAST -lLLVMBitReader
-lclangAnalysis -lclangEdit -ldl -lclangDriver -lpthread -ltinfo -lclangParse
-lLLVMOption -lLLVMProfileData -lz -lclangLex -lLLVMSupport -lclangBasic
-lclangSema -lLLVMMCParser -lLLVMMC
That took a long time to figure out, and, even worse, it changes from Clang
version to Clang version.
My tool does not require Clang source, and it's quite inconvenient for users to
keep the Clang source tree around just to leverage its build process for a tool
that otherwise has no dependence on Clang source. A clang-config tool would be
a great help in this and similar situations.
Thanks for your consideration,
-- Scott</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>