-
Notifications
You must be signed in to change notification settings - Fork 7
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
Gradle error matching doesn't work with row:column format #12
Comments
With this error match I'm able to get atom to recognize errors in gradle c++ builds. The last match is what was already in build-gradle, but it doesn't work with hpp and cpp matches I created. Not sure in which cases that match is used.
|
Mind posting your whole log? I initially created the match with Java, Scala, and Groovy in mind. |
Sure, thank you for taking a look. The build is gcc running in gradle (standard native build in gradle). Native builds are not that popular, but it's a great substitution to cmake. The issue I have is when the include file is not available from hpp file. In that case there are at least two paths: for the top cpp, and for the existing hpp (that has missing hpp include). |
For those searching for kotlin matchs patern it's: |
Gradle error about missing header is not parsed correctly (native C++ compilation). Example of error message (notice filename:row:col: message format):
/.../Src/ProcessImageDataProvider.cpp:3:24: fatal error: OsAssert.hpp: No such file or directory
compilation terminated.
The text was updated successfully, but these errors were encountered: