LibTooling and kdev-clang

Milian Wolff mail at milianw.de
Thu May 28 13:52:12 UTC 2015


Hey Maciej,

please send such emails to the kdevelop-devel at kde.org mailing list, so that 
all others can see what you are doing and chime in as necessary.

On Wednesday 27 May 2015 22:25:24 Maciej Poleski wrote:
> Hi
> 
> I've just hit very unpleasant impediment. ClangTool contains FileManager,
> but does not provide way of customizing it. It's trivial but very
> unpleasant as everything is on place with one tiny exception:
> http://clang.llvm.org/doxygen/Tooling_8cpp_source.html#l00278
> 
> This issue is trivial to fix (example: provide additional optional parameter
> in constructor - vfs::FileSystem), but even having this fixed upstream now
> is too late for us.
> 
> I see two solutions here:
>  - Leave default here (flushing KDevelop caches before any refactoring), and
> customize VFS in place of application of Replacements (yes it is possible
> here (!) as Rewriter contains SourceManager) which would be used then in
> tooling::applyAllReplacements - Leave default here (as above), and forget
> about VFS. Translate Replacements into DocumentChangeSet.
> 
> I asked about possible workaround on Clang mailing list, but don't hope for
> a solution.
> 
> Let me know if You have any preferences here.

Can you give some more context here? What do you want to do exactly, or what 
is the issue? I just see that ClangTool has a getFiles returning a non-const 
reference to the FileManager - is that not enough?

Bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de


More information about the KDevelop-devel mailing list