Open kaby76 opened 10 months ago
java -jar C:\Users\Kenne\.m2\antlr4-4.13.1-complete.jar c:\msys64\home\Kenne\issues\g4-3810\abb\abbLexer.g4
does not generate any files. (No -o
, full path grammar file name.)java -jar C:\Users\Kenne\.m2\antlr4-4.13.1-complete.jar \msys64\home\Kenne\issues\g4-3810\abb\abbLexer.g4
does not generate any files. (No -o
, full path grammar file name, no drive letter.)java -jar C:\Users\Kenne\.m2\antlr4-4.13.1-complete.jar c:\\msys64\\home\\Kenne\\issues\\g4-3810\\abb\\abbLexer.g4
does not generate any files. (No -o
, full path grammar file name, multiple backslash.)java -jar C:\Users\Kenne\.m2\antlr4-4.13.1-complete.jar c:/msys64/home/Kenne/issues/g4-3810/abb/abbLexer.g4
WORKS! (No -o
, full path grammar file name but using forward slashes.)0
even though it did not generate a parser. If the tool cannot generate the code it should raise an error so the build stops.
Antlr tool does not generate files for a grammar if the path given is a full, rooted path. The following is a session in a "cmd.exe" shell. Notice there are no .java files in the directory before or after running the command "java -jar ..." for a path with a drive_letter.
The tool cannot work without the
-o
option on Windows with full-path file names.If you thought that the
-o
option would work always, it turns out not to either. The tool also does not work with paths with a drive letter.The .log files show that the tool certainly has no problem opening and reading the .g4 file. It appears to be a problem with the output directory.