You can run ANTLRWorks and tell it to generate the output code or you can run ANTLR directly from the commandline with:
Better yet, add the jar antlr-3.1.2.jar to your
Running ANTLR with no parameters shows you:
usage: java org.antlr.Tool [args] file.g [file2.g file3.g ...]
-o outputDir specify output directory where all output is generated
-fo outputDir same as -o but force even files with relative paths to dir
-lib dir specify location of token files
-depend generate file dependencies
-report print out a report about the grammar(s) processed
-print print out the grammar without actions
-debug generate a parser that emits debugging events
-profile generate a parser that computes profiling information
-nfa generate an NFA for each rule
-dfa generate a DFA for each decision point
-message-format name specify output style for messages
-verbose generate ANTLR version and other information
-X display extended argument list
For example, consider how to make the LL-star example from the examples tarball you can get at http://www.antlr.org/download/examples-v3.tar.gz.
$ cd examples-v3/java/LL-star
$ java org.antlr.Tool SimpleC.g
$ javac *.java
In above command, we are considering ANTLR3 jar lies in your classpath.
you will see output as follows:
$ java Main input
bar is a declaration
foo is a definition
What if I want to test my parser without generating code? Easy. Just run ANTLR in interpreter mode. It can't execute your actions, but it can create a parse tree from your input to show you how it would be matched. Use the org.antlr.tool.Interp main class. In the following, I interpret simplec.g on t.c, which contains "int x;"
$ java org.antlr.tool.Interp simplec.g WS program t.c
( <grammar SimpleC>
( type [@0,0:2='int',<14>,1:0] )
( declarator [@2,4:4='x',<2>,1:4] )
where I have formatted the output to make it more readable. I have told it to ignore all WS tokens.