[cfe-commits] [cfe-dev] Announcing an official home for tools built on the Clang platform, as part of the Clang project

[Chandler Carruth]

Can you call the tool 'template-tool' and 'TemplateTool'?

Can you add some boring printing to stdout and then write a boiler plate
test so that we ensure the template keeps running (in addition to building)?

Finally, can you update the README to mention this template? Maybe in a
separate change update the HTML docs too?

Thanks for working on this!


On Tue, Aug 14, 2012 at 7:07 AM, Marshall Clow <mclow.lists at gmail.com>wrote:

> [ Resending to cfe-commits because apparently I'm still asleep ]
>
> On Aug 14, 2012, at 12:58 AM, Chandler Carruth <chandlerc at google.com>
> wrote:
>
> Hello everyone!
>
> As you may have noticed with various email and commits going about
> recently, we're opening up an official home and structure for developing
> developer-facing tools as part of the Clang project.
>
> This is intended to be a place where the community can develop refactoring
> tools, analysis tools, and other code-oriented, Clang-based tools that make
> writing C, C++, Objective C, and Objective C++ code easy and fun.
>
> I've started seeding documentation about this, currently oriented mostly
> at fellow tool developers. As we build a collection of tools, we'll be
> working on better user-facing documentation and packaging, but the
> immediate pressing need is to get a good place to collaborate on these
> tools together, and start building awesome new things.
>
> Documentation: http://clang.llvm.org/docs/ClangTools.html
> Repository: http://llvm.org/svn/llvm-project/clang-tools-extra/trunk
> Git mirror: http://llvm.org/git/clang-tools-extra.git
> Getting started: http://clang.llvm.org/get_started.html
>
> I've added one of the tools that we built here at Google when initially
> developing this framework as an example of how tools in this tree should be
> structured. It's not the best tool, but it is simple and a good starting
> point. The build systems (both Makefiles and CMake) have been updated so
> that the extra repository should just work when dropped in the right place.
>
> We're hoping to get several more tools that have already started to be
> developed by the community moved into a new home here. However, we're still
> ironing out the exact criteria for accepting tools into the Clang project.
> I want to emphasize -- this separate repository is a technical division to
> enable thinner checkouts of Clang when that is useful. This is not a new or
> separate project, it is very much part of the Clang project and community,
> and is being run by the same community. =]
>
>
> Here's a patch that implements a "skeleton" refactoring tool; i.e, a
> starting point for the development of other tools.
> It contains all the boilerplate stuff needed to get a tool up and running,
> missing only the AST matchers to find the things to refactor, and the code
> to actually change the code.
>
> Works with this morning's TOT.
>
>
> -- Marshall
>
> Marshall Clow     Idio Software   <mailto:mclow.lists at gmail.com<mclow.lists at gmail.com>
> >
>
> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is
> promptly moderated down to (-1, Flamebait).
>         -- Yu Suzuki
>
>
>
> _______________________________________________
> cfe-commits mailing list
> cfe-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20120814/5e276f61/attachment.html>