-
Notifications
You must be signed in to change notification settings - Fork 54
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
Visual Studio Code "gpr-aware" problemMatcher ? #541
Comments
You're right @JHag6694 - at the moment I would pass |
Thanks @setton for the option. Works fine |
Hello @terids - unfortunately this doesn't exist yet - we will need to write some code that processes the .gpr file and gets the list of file from it, in order to match base name to file name... we plan to work on this, but we don't have a date in mind yet. |
Hello @terids Here attached, you will find my tasks.json which is working fine. |
@JHag6694 the absolute path did it for me, thanks so much for that :) |
and fix examples by adding `-gnatef` to `tasks.json` Refs #541
and fix examples by adding `-gnatef` to `tasks.json` Refs #541
I've added a "auto-detected tasks" that work well with "$ada" problem matcher using absolute file names ( out.mp4 |
I think this works now (with |
Hi
Start to evaluate ALS using the Visual Studio Code extension.
In the build task provided , problemMatcher is set to "$ada"
If I use the same task with my own projects, it sems that it will only let me jump to the correct file/line when the build task displays an error if .gpr and .adb are in the same folder - as only the source file base name is displayed and problemMatcher is not "gpr-aware"
Am I right or did I miss something ?
The text was updated successfully, but these errors were encountered: