-
Notifications
You must be signed in to change notification settings - Fork 108
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
Fix build issues on Mac and Linux #252
Conversation
Ok, clearly the tool behaves differently under Windows vs Unix wrt output paths... |
@@ -14,7 +14,7 @@ import { ParseInfo } from "./atn/ParseInfo"; | |||
import { ProxyErrorListener } from "./ProxyErrorListener"; | |||
import { RecognitionException } from "./RecognitionException"; | |||
import { RuleContext } from "./RuleContext"; | |||
import { SuppressWarnings, NotNull } from "./decorators"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line prevents the module working on Linux
@carlansley ❗️ We won't be able to review this pull request until you submit a pull request to antlr/antlr4 to add your name to the contributors.txt agreement. In lieu of signing the agreement, you could file issues here describing the specific problems you encountered and we could independently implement solutions to them. 😄 |
@carlansley, are things working for you now? |
Been a while since I've looked at this. It was working for me, not sure if I'd done something to make it work, but I think at least some of my issues at the time were fixed in master (e.g. case sensitive filename issues). However on a fresh clone of master on my Mac, I now get thousands of
|
Those missing files under ./gen are almost certainly an indication you need to run the whole build process by invoking |
These errors occur during the npm install. |
Please make sure you have the build prerequisites (Java & Maven) installed. Executing If the errors are due to that, we should probably add a more explicit check to the NPM build script in package.json. |
Both are installed:
This has worked in this environment. I believe there is an issue with the generated ts files being put in the wrong directory location in Mac (and maybe Linux) environments. |
Notice the first error from
It's putting it in |
During build, this is what I see on Windows generating those files. I notice it includes a "
|
This PR gets npm install working on Mac and Linux due to various path & case-sensitive filename issues. A fresh install also doesn't currently compile with the latest typescript 2.1, so fixed TS version at 2.0.8.
Haven't tested this under Windows.