[cfe-commits] Moves clang-check from examples/Tooling into tools (issue4449067)

[Chandler Carruth]

On Thu, Apr 28, 2011 at 2:23 PM, Manuel Klimek <klimek at google.com> wrote:

> On Thu, Apr 28, 2011 at 2:03 PM, Chris Lattner <clattner at apple.com> wrote:
> >
> > On Apr 28, 2011, at 1:57 PM, klimek at google.com wrote:
> >
> >> Reviewers: chandlerc,
> >>
> >> Description:
> >> Looks like it should have been there all along - clang-check is a useful
> >> tool for quick feedback editor-integration.
> >>
> >> Please review this at http://codereview.appspot.com/4449067/
> >
> > One of the reasons that it isn't in tools is that we don't want to build
> it all the time.  The incremental cost of linking all the libraries into
> yet-another-tool is quite high.  Why is this useful?
>
> >From our experience at Google this is one of the favorite tools of our
> developers, as it allows fast feedback while coding from vi or emacs
> without the need to invoke the build.


Yea, in particular, this was seen as a really killer tool when folks rigged
up a ":clang_check" vim or emacs command that would invoke it on the file in
the current buffer after a quick save. It's basically a way to get the
"clang compile" button of xcode into other environments.

That said, if its slowing down builds, is there a way we can mark specific
tools as optional? It seems more important to have the code and the tool be
discoverable in the tree than be built every time if people aren't using
it...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20110428/7416bd6f/attachment.html>