Skip to content
No description or website provided.
C++
Pull request Compare This branch is 12 commits behind chisophugis:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
.gitignore
FindDependencies.cpp
Makefile
README.rst

README.rst

Quickstart

Run ./try and hopefully you'll see a huge list of headers spewed out. If that didn't work, contact me (chisophugis@gmail.com) immediately and I will fix it.

Goal

The goal of this is to be a really clear and simple tutorial on how to do useful stuff with clang. I'm hoping it will make a good "Hello World" for people new to clang; that's exactly what I found most sorely lacking documentation-wise for clang (and LLVM in general), and my experience was so distasteful that I feel impelled to fix the situation.

However, the doxygen docs are fantastic! Once you make it past the inital hurdle of the "Hello World", it's pretty smooth sailing.

Improvements

Contact me immediately if

  • you have any trouble whatsoever with this example program
  • find anything insufficiently explained (even the Makefile!)
  • find any explanations unclear
  • you come up with a small tweak that could make the program more interesting
  • have a suggestion for something that you would like to see the program do that you think would make an interesting "Hello World"

Contribute

Clang needs these kinds of minimal tutorials to get people up and running quickly. If you try this out, fork the repo! Then if you make something even remotely interesting, send me a pull request and I'll add it to the collection (obviously I'll organize things better if that happens).

Some ideas:

  • Add a RecursiveASTVisitor and scrape interesting statistics about your program (i.e. how many while loops are there in a source file?). You'll need a custom ASTConsumer that hands off to the RecursiveASTVisitor. Check the doxygen.
  • Inject the FindDependencies plugin into the build of a project (why not LLVM/Clang?) then run some graph algorithms on the result.
Something went wrong with that request. Please try again.