| 1 | Getting compile errors in this plugin? Wondering why? Keep on reading! |
| 2 | |
| 3 | This file describes how to build the CTF Java parser files. They are not stored |
| 4 | in the git repository anymore, and must be generated by the build system. |
| 5 | |
| 6 | Unfortunately there is no easy way to setup an Eclipse builder to generate those |
| 7 | files, since the Antlr plugin in Orbit only provides the runtime, and not the |
| 8 | tool to generate Java files. |
| 9 | |
| 10 | You have two options: |
| 11 | - On Linux distros: |
| 12 | You can install Antlr 3.2, and then run the generate-grammar.sh script in this |
| 13 | directory. On Ubuntu 12.04, getting Antlr is a simple |
| 14 | $ sudo apt-get install antlr3 |
| 15 | |
| 16 | The files were only tested with Antlr 3.2 though, so they might not compile |
| 17 | with other versions. |
| 18 | |
| 19 | - On all systems: |
| 20 | For a more cross-platform solution you can use Maven to generate the parser |
| 21 | files. If you have Maven installed on your system, you can cd into this |
| 22 | directory and type "mvn install" in a terminal. |
| 23 | |
| 24 | Another option is to install the Maven Eclipse integration plugin "m2e". It |
| 25 | can be found in the default Eclipse repository (under "Collaboration"). Once |
| 26 | it's installed, you can right-click the pom.xml file in this directory and |
| 27 | choose Run As -> Maven install. |
| 28 | |
| 29 | Both methods should create the Java files and put them in the correct directory. |
| 30 | You may need to refresh the project, after which the compilation errors should |
| 31 | disappear. |