[cfe-dev] Loading plugins into libclang
Benjamin Kramer via cfe-dev
cfe-dev at lists.llvm.org
Tue Mar 1 08:40:13 PST 2016
On Tue, Mar 1, 2016 at 4:37 PM, Kevin Funk <kfunk at kde.org> wrote:
> On Tuesday, March 01, 2016 02:16:52 PM Benjamin Kramer via cfe-dev wrote:
>> Hi everyone,
>> in my quest to get clang-tidy integrated into your favorite editor
>> (via ycm) I'm hitting one major roadblock. I'm piggybacking on the
>> existing plugin mechanism which gives me both a way to add extra
>> Actions to the parse process and hand flags to the plugin for
>> configuration. This works well for (most of) clang-tidy as it really
>> just emits diagnostics and FixIts.
> did you see my patch here?
> This makes it possible to load Clang plugins in libclang by simply passing
> additional compiler arguments to libclang's clang_parseTranslation function.
>> However, loading a plugin into libclang isn't easily possible because
>> there it doesn't export all the clang symbols.
> I'm not sure I understand this issue. Could you elaborate?
> A Clang plugin is supposed to be linked against all necessary Clang/LLVM
> libraries already, isn't it? So it should be possible to dlopen the plugin
> just fine.
Oh I see. I was holding CMake wrong, actually linking all of Clang and
Clang-tidy into the same .so works. This is a bit scary to me because
there are now two clang copies around but it seems to work fine.
>> Putting all the clang
>> symbols into the plugin doesn't work either because you'll get
>> duplicate command line flag registration and everything. My current
>> hack is to statically link clang-tidy into libclang. This works but
>> creates an ugly (optional) dependency from libclang into
>> Is there any other way to extend libclang without actually modifying
>> libclang itself?
>> - Ben
>> cfe-dev mailing list
>> cfe-dev at lists.llvm.org
> Kevin Funk | kfunk at kde.org | http://kfunk.org
More information about the cfe-dev