[Qt-creator] Qt Creator Issues tab does not populate

[Tobias Hunger]

Hello Alfonso!

2013/3/8 Alfonso Chartier <alfonso.chartier at gmail.com>:
> Compiling "C:\spa_z\spa_dsp\TgUmts\TgUmts_oneNand.c"
> Assembling "TgUmts_oneNand.src"
> Compiling "C:\spa_z\spa_dsp\TgUmts\TgUmts_channel.c"
> c563 W135: C:\spa_z\spa_dsp\TgUmts\TgUmts_channel.c: line 2089: statement
> not reached
> c563 W135: C:\spa_z\spa_dsp\TgUmts\TgUmts_channel.c: line 2095: statement
> not reached

None of our parsers will read that properly.

> Is this output formatted as other standard compilers? By the way, this
> output in Qt Creator shows up all black (no red, so I assume it's all going
> to stdout?).

All black is stdout, yes.

> For reference, this is the custom error parser regular expression string
> configured in CodeWright:
>
> ^.*([^ \t]*): line ([0-9]+) *: (.*)$
>
> I believe the wmk.exe program internally calls another tool called mk563,
> which is a program we can call directly and seems generally similar to
> regular make. Below are its available options (although I don't really see
> an equivalent make -w option):

The -w is necessary to find possible base directories for turning relative paths
into absolute ones. That does not seem necessary for your setup.

<hack>
One more hack to avoid changing the code in creator:
You could try doing a wrapper script around wmk that just passes its
arguments on
to wmk and passes wmks output through unmodified unless it matches the regexp
above. In that case it could turn it into a gcc-like message
(file:line: (warning|error):
message) and pass that to stderr where gcc puts its error messages.

Then you can set up that wrapper as a "make" in a makestep and configure creator
to expect gcc output.
</hack>