Hi Manuel, On Mon, Aug 26, 2013 at 9:39 AM, Manuel Klimek <[email protected]> wrote: > > I'm still not sure what exactly the problem is. It seems to me like you > could implement a clang-tool and a clang plugin with very little overhead.
I just wanted to come back to this, even though I don't seem to be having any luck in explaining myself. It definitely seems possible to implement, but I still question why it is that tools cannot/do not pick up input files from Clang's command-line. It seems like that would make them immediately pluggable into make systems without any obvious drawbacks. I entertain the possibility that I'm wrong, though :-) >> John's latest patch was exactly what I was looking for, however: if >> findInputFile(s) was part of Tooling proper, I could use it to unpack >> the inputs from the Clang command-line and feed it into ClangTool. > > As I said, putting findInputFiles into a better place (probably the driver > library) would make sense, if somebody wants to tackle it :) I'd be happy to do that if there's interest. I'll probably need it before too long anyway. Thanks, - Kim _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
