[llvm-bugs] [Bug 32080] New: Need clang-config tool

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=32080

            Bug ID: 32080
           Summary: Need clang-config tool
           Product: clang
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: -New Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: scott+llvm+bugzilla at pakin.org
                CC: llvm-bugs at lists.llvm.org

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

-- 
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/20170227/fc2a1e7d/attachment.html>