1

I am writing code in WSL using a remote session and then building on cmd.exe. The build process works fine but I cannot get the problem matcher to link to the correct files.

I change my cwd 

"options": {
    "cwd": "/mnt/c/Freescale/CW MCU v10.6.4/eclipse"
  },

Below is my build cmd

 "cmd.exe /c ecd.exe build -data $WORKSPACE_LOC -project $PROJECT_LOC"

Problem matcher looks like 

"problemMatcher": {
    "base": "$gcc",
  }

Any suggestions on how to solve this. I have tried using relative and absolute paths.

Ali
  • 11
  • 1
  • Does the build task actually output the error lines, or does it just produce an output file? – Brad Feb 20 '21 at 00:40
  • I think it produces an internal file and uses a regex-based problem matcher to parse data. – Ali Mar 10 '21 at 22:14
  • Not asking about the problem matcher, asking about ecd.exe. The problem matcher consumes standard output from the command (cmd.exe /c ecd.exe ...). So, if ecd.exe is writing the output to a log of it's own, then the problem matcher won't see it. There isn't really enough detail for me to tell for sure, but I'm guessing you need to run a build.cmd file that does ecd.exe ... and then "cat"s that to the stdout so the command in the task list sees it. – Brad Mar 13 '21 at 02:23

0 Answers0