MontiCore - Getting Started
In the following you will learn how to get started with MontiCore. Before you start please make sure that Java is installed on your system as described in the prerequisites. Now that your system is ready you have three options to get started. Just choose one of the following guides:
- Install the Java 8 JDK.
- Make sure the environment variable JAVA_HOME points to the installed JDK, NOT the JRE (e.g. ‹/usr/lib/jvm/java-8-openjdk› on UNIX or ‹C:\Program Files\Java\jdk1.8.0_51› on Windows). You will need this in order to run the Java compiler for compiling the generated Java source files; see here for more information.
- Also make sure that the PATH variable is set such that the Java compiler is available. JDK installations on UNIX systems do this automatically. On Windows systems the ‹bin› directory of the JDK installation needs to be appended to the PATH variable, e.g. ‹%PATH%;%JAVA_HOME%\bin› (see also here).
MontiCore supports different environments. For a quick peek, the command line version can be tried out with an exemplary automata DSL using the following instructions:
In a nutshell
|Prerequisites||Install the Java Development Kit (JDK) 8.|
|Installation||Download the MontiCore distribution file, unzip it, and change to the extracted directory.|
|Running MontiCore||Execute MontiCore on the provided language definition ‹Automata.mc4›.|
|Compiling the Product||Compile all the generated and supplied handwritten Java source files.|
|Running the Product||Execute the automata tool on an example model ‹example/PingPong.aut›.|
- Download the MontiCore zip distribution file.
- Unzip the distribution. It will unzip a directory called ‹mc-workspace› containing the executable MontiCore CLI (short for command line interface) JAR along with a directory ‹src› containing handwritten automata DSL infrastructure, a directory ‹hwc› containing handwritten code that will be incorporated into the generated code, and a directory ‹example› containing an example automata model.
- Open a command line interface and change to the unzipped directory ‹mc-workspace›).
- The distribution contains the sources of an automata DSL consisting of the automata grammar and handwritten Java files in the directory ‹src›. Execute the following command in order to generate the language infrastructure of the specified automata DSL:
java -jar monticore-cli.jar -g Automata.mc4 -hcp hwc/ -mp monticore-cli.jar
The only required argument ‹Automata.mc4› denotes the input grammar for MontiCore to process and generate the language infrastructure for. The second argument denotes the path to look for handwritten code that is to be incorporated into the generated infrastructure. MontiCore will be launched and the following steps will be executed:
- The specified grammar will be parsed and processed by MontiCore.
- Java source files for the corresponding DSL infrastructure will be generated into the default output directory ‹out›. This infrastructure consists of:
- out/automata/_ast containing the abstract syntax representation of the automata DSL.
- out/automata/_cocos containing infrastructure for context conditions of the automata DSL.
- out/automata/_od containing infrastructure for printing object diagrams of the automata DSL.
- out/automata/_parser containing the generated parsers which are based on ANTLR.
- out/automata/_symboltable containing infrastructure for the symbol table of the automata DSL.
- out/automata/_visitor containing infrastructure for visitors of the automata DSL.
- out/reports/Automata containing reports created during the processing of the automata grammar.
- The output directory will also contain a log file of the executed generation process ‹monticore.YYYY-MM-DD-HHmmss.log›.
Compile and run
- Compiling the automata DSL
- Execute the command:
javac -cp monticore-cli.jar -sourcepath "src/;out/;hwc/" src/automata/AutomataTool.java
Please note: on Unix systems paths are separated using ":" (colon) instead of semicolons.
This will compile all generated classes located in ‹out/› and all handwritten classes located in ‹src/› and ‹hwc/›. Please note that the structure of the handwritten classes follows (though not necessarily) the package layout of the generated code, i.e. there are the following sub directories (Java packages):
- src/automata contains the top level language realization for using the generated DSL infrastructure. In this case the class ‹src/automata/AutomataTool.java› constitutes a main class executable for processing automata models with the automata DSL (inspect the class and see below for how to execute it).
- src/automata/cocos contains infrastructure for context condition of the automata DSL.
- src/automata/prettyprint contains an exemplary use of the generated visitor infrastructure for processing the parsed model. Here: for pretty printing.
- src/automata/visitors contains an exemplary analysis using the visitor infrastructure. The exemplary analysis counts the states contained in the parsed automata model.
- hwc/automata/_ast contains an exemplary usage of the handwritten code integration mechanism for modifying the AST for the automata DSL.
- hwc/automata/_symboltable contains handwritten extensions of the generated symbol table infrastructure.
- Running the automata DSL tool
- Execute the command:
java -cp "src/;out/;hwc/;monticore-cli.jar" automata.AutomataTool example/PingPong.aut
Please note: on Unix systems paths are separated using ":" (colon) instead of semicolons. This will run the automata DSL tool. The argument ‹example/PingPong.aut› is passed to the automata DSL tool as input file. Examine the output on the command line which shows the processing of the example automata model.
- Execute the command:
The shipped example automata DSL (all sources contained in ‹mc-workspace/src› and ‹mc-workspace/hwc›) can be used as a starting point. It can easily be altered to specify your own DSL by adjusting the grammar and the handwritten Java sources and rerunning MontiCore as described above.
The Eclipse or IntelliJ version of the Getting Started can be found here:
- If an error occurs and you cannot solve the problem you may take a look into the MontiCore log file located in the respectively specified output directory (e.g. ‹out/monticore.YYYY-MM-DD-HHmmss.log› by default). It contains more verbose and developer-oriented, technical output than the CLI output.
- Please report any unknown issues to firstname.lastname@example.org. Please include the processed grammar, model, and the log file.