You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a build task that uses the gcc problemMatcher, but the output has file paths that need to be transformed in order to match with the source locally.
I haven't found the documentation detailing all the features supported by fileLocation; the typical defaults "autoDetect" and "${workspaceFolder}/src" are not doing me much good atm.
Can I remap the paths or use a regexp in some way? In gdb world, this is what we do: set substitute-path /data_docker G:/project/src .. how can I do the same in problemMatcher?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have a build task that uses the gcc problemMatcher, but the output has file paths that need to be transformed in order to match with the source locally.
I haven't found the documentation detailing all the features supported by
fileLocation
; the typical defaults"autoDetect"
and"${workspaceFolder}/src"
are not doing me much good atm.Can I remap the paths or use a regexp in some way? In gdb world, this is what we do:
set substitute-path /data_docker G:/project/src
.. how can I do the same in problemMatcher?Beta Was this translation helpful? Give feedback.
All reactions