-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No longer can generate parsers #306
Comments
😕 I haven't made any releases any time recently. Were you using a non-Windows system by any chance? If so you were probably hitting #303. |
Yes, that looks related. I'm on macOS and the code generation used to work before. As a workaround I copied the jar to my grammar folder and generated my grammars directly without antlr4ts-cli. |
I just realized that I also need the code generation for getting the ATN for a given grammar, so it's quite essential for me that this gets fixed soon. Sorry for the extra pressure but I'm blocked here currently. |
Duplicate of #303 |
@sharwell I added |
I haven't done this for a while (and it worked before) but with the latest antlr4ts package generating files from grammars fails. The problem is that paths are now handled different than before and I'm not 100% sure this is a problem of antlr4ts and not, maybe, by vscode (where I use this node module).
What happens is this:
As you can see my 3 grammar files are located in a subfolder called grammars.
The problem here is that the output is not placed in the parser subfolder as specified, but in parser/grammars. Well, actually only the output for the first grammar. Further generation fails then because these generated files are not found.
I'm using the latest antlr4ts and antlr4ts-cli node modules.
The text was updated successfully, but these errors were encountered: