Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
A collection of code samples showing usage of clang and llvm as a library
C++ Makefile C
Branch: master

Fixes #26

After more investigation the JSON parser inside clang is very liberal in what
it accepts so this worked just fine in testing but it was a typo and wasn't
strictly speaking correct.
latest commit a21409027c
@loarabia authored
Failed to load latest commit information.
Win Fix Windows Build Break against mainline.
.gitignore Add Tooling example.
CIBasicRecursiveASTVisitor.cpp Repair more advanced tutorials.
CIrewriter.cpp Repair more advanced tutorials.
CItutorial1.cpp Fix CI tutorials.
CItutorial2.cpp Fix CI tutorials.
CItutorial3.cpp Fix CI tutorials.
CItutorial4.cpp Fix CI tutorials.
CItutorial6.cpp Repair more advanced tutorials.
CREDITS.txt Add credits.
CommentHandling.cpp Fixing the last of the tooling tutorials.
LICENSE.txt Fix the License.
README.markdown Update readme for last build date
ToolingTutorial.cpp Fixing the last of the tooling tutorials.
compile_commands.json Fixes #26
input04.c Fix tutorial 6 to match the writeups.
invalidInputTest.c Handle outputing parsing error cases
makefile Fixing the last of the tooling tutorials.
test.c Updated the comments to point to the LICENSE.
testInclude.c Updated the comments to point to the LICENSE.
test_rewriter.cpp Repair more advanced tutorials.
tutorial1.cpp Repairing tutorial.
tutorial2.cpp Repairing tutorial.
tutorial3.cpp Final set of repairs for the original tutorials.
tutorial4.cpp Final set of repairs for the original tutorials.
tutorial6.cpp Final set of repairs for the original tutorials.

README.markdown

About

This is a collection of tutorials showing off how to use core Clang types. It is based directly on two older tutorials which no longer built due to code rot.

  1. tutorial 1 by Nico Weber - 9/28/2008
  2. tutorial 2 by Justin LaPre at Rensselaer Polytechnic Institute - 10/20/2009
  3. tutorial 3 by Larry Olson - 4/14/2012

This particular set of tutorials tracks the llvm / clang mainline and is updated semi-regularly to account for llvm / clang API changes.

See contents of the links above for a walkthrough of what these tutorials are doing.

Last Update

This was last built on 5/25/2015 against
URL: http://llvm.org/svn/llvm-project/llvm/trunk
Revision:237487

Other Options

The Clang team has been hard at work making it easier to write tools using Clang. There are 4 options for developing tools using clang and llvm infrastructure.

Latest Stable LLVM / Clang (v3.4)

The master branch tracks recent commits to the clang and llvm svn. The tutorial assumes you have grabbed a copy of both llvm and clang by following these instructions and that you have modified the makefile of this project to point to the build's resulting llvm-config. If you want the latest public release, then checkout the 3.4 branch.

git clone git@github.com:loarabia/Clang-tutorial.git
git checkout 3.4

CI tutorials

The tutorials prefixed with CI are the same as the original tutorials but use the CompilerInstance object and its helper methods to perform the same tasks as the original tutorials. For the most part, this makes the code much more compact.

Tooling tutorials

These tutorials (and the clang tooling infrastrucutre) depend on having a file called compile_commands.json which defines the commands used to compile the input file. You will need to modify this file's directory field to point to the absolute path of the Clang-tutorial on your storage.

Update compile_commands.json to the directory containing input

./ToolingTutorial input04.c
./CommentHandling input04.c

Windows Build

Note on the Windows build: Currently the paths are hardcoded. Please see the SharedBuild.targets file inside of the SharedBuild project to update the path for your specific LLVM and CLANG install.

In particular, the LLVMLibsDirs property and the LLVMIncludes property should be updated.

Contact Me

For any questions, please ping me via my github account. Changes and additions are always welcome.

Something went wrong with that request. Please try again.