[llvm-bugs] [Bug 28283] New: writing clang plugins should not require a clang build

[via llvm-bugs]

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

            Bug ID: 28283
           Summary: writing clang plugins should not require a clang build
           Product: clang
           Version: 3.7
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: libclang
          Assignee: unassignedclangbugs at nondot.org
          Reporter: jhi at iki.fi
                CC: klimek at google.com, llvm-bugs at lists.llvm.org
    Classification: Unclassified

I tried to get started writing clang plugins, again, and was, again, thwarted
by the need to have a fresh build of clang around.  Not an installation, a
build.

I can build llvm and clang, it's just that I find it a little ... awkward? 
clunky? to need to have the objects and the whole build tree around, to be able
to write plugins.

Moreover, practically none of the examples found in the Internet work, because
they were written for some earlier releases of clang.  I understand that
keeping the plugin interface stable may not be the highest priority.  I guess
the latest clang plugin tutorial works for the latest source release, one would
hope, but probably not for the HEAD of the repo, anymore...

But I guess my main gripe is: a clang binary distribution should include
everything required to write plugins.  The very definition of plugin to me says
that the whole thing does not need to be modified.

-- 
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/20160624/74863808/attachment.html>