| java.lang.Object
 org.antlr.tool.BuildDependencyGenerator
| BuildDependencyGenerator | | public class BuildDependencyGenerator (Code) | | Given a grammar file, show the dependencies on .tokens etc...
Using ST, emit a simple "make compatible" list of dependencies.
For example, combined grammar T.g (no token import) generates:
TParser.java : T.g
T.tokens : T.g
T__g : T.g
For tree grammar TP with import of T.tokens:
TP.g : T.tokens
TP.java : TP.g
If "-lib libdir" is used on command-line with -depend, then include the
path like
TP.g : libdir/T.tokens
Pay attention to -o as well:
outputdir/TParser.java : T.g
So this output shows what the grammar depends on *and* what it generates.
Operate on one grammar file at a time. If given a list of .g on the
command-line with -depend, just emit the dependencies. The grammars
may depend on each other, but the order doesn't matter. Build tools,
reading in this output, will know how to organize it.
This is a wee bit slow probably because the code generator has to load
all of its template files in order to figure out the file extension
for the generated recognizer.
This code was obvious until I removed redundant "./" on front of files
and had to escape spaces in filenames :(
|
| templates | | protected StringTemplateGroup templates(Code) | | |
| BuildDependencyGenerator | | public BuildDependencyGenerator(Tool tool, String grammarFileName) throws IOException, antlr.TokenStreamException, antlr.RecognitionException(Code) | | |
| getDependencies | | public StringTemplate getDependencies()(Code) | | |
| getDependenciesFileList | | public List getDependenciesFileList()(Code) | | Return a list of File objects that name files ANTLR will read
to process T.g; for now, this can only be .tokens files and only
if they use the tokenVocab option.
|
| getGeneratedFileList | | public List getGeneratedFileList()(Code) | | From T.g return a list of File objects that
names files ANTLR will emit from T.g.
|
| loadDependencyTemplates | | public void loadDependencyTemplates()(Code) | | |
|
|