Open FrankHileman opened 2 years ago
For whatever reason, it's trying to run java.exe, and it has a hard time finding D:\Frank\Visual Studio Projects\DASH\NGAW2\AntlrTest\Arithmetic.g4
, which is rather surprising because I have double quotes surrounding everything in the Process.Start() call. I'll fix it tonight or tomorrow. It's not a problem with the Antlr4Templates.
Thank you for point this error out. There were a number of problems fixed. I released 9.3 of Antlr4BuildTasks, and an updated set of templates in 1.4 of Antlr4Templates. --Ken
Hello, Thanks again. Are you planning on pushing 1.4 of Antlr4Templates soon? I didn't see that in the commits yet.
Sorry, I didn't check the changes in. Done. I made a release 1.4 of the templates here: https://www.nuget.org/packages/Antlr4Templates/1.4.0
The names of the console apps have changed. There is now a Java application template as well. So, the standard "combined" Antlr grammar (which has both lexer and parser rules in one file) is named "csharp-combined". Other templates are "csharp-split", "java-combined" and "java-split". I changed the names because I plan to add templates for the other Antlr targets. Note, it only creates an app for the Arithmetic.g4 grammar.
Everything seems to work now, with a new project. There are some minor issues with the templates, you probably know about. Simply things that code analysis will point out. And the default namespace. Thanks again. Antlr is my favorite parser generator, so I am happy to see other people working on C# based tools. The template produced program is very good to get started.
Thanks for all your hard work on these Antlr repositories. I am not sure if this is a problem with Antlr4Templates, or Antlr4BuildTasks.
I used Antlr4Templates, specifically the antlr4 template, to create a new project in a new directory. This built fine.
Then I opened the project in Visual Studio and upgraded the nuget package Antlr4BuildTasks to version 9.2.0. Now the project does not build. I have spaces in the project path, and this seems to cause the problem: when processing "Visual Studio Projects" it is breaking up the path at "Studio":