Qt Creator not parsing arm-none-eabi-gcc compile output into issues
I am using meson (ninja) to build with arm-none-eabi-gcc.
I have set a custom build step: ninja
with arguments (to redirect to sterr): 3>&1 1>&2 2>&3
When I build, I can see the output in the "compile output" pane but I cannot click on the file/line numbers there, nor are they populated in the "issues" tab.
I have the Clang Code Model disabled, if that makes any difference. Qt Creater version 4.9.0.
Any ideas? Perhaps I need to set arm-none-eabi-gcc as a recognised compiler somehow?
@justyn can you give an example of that output? are the lines red or black in Creators compile output?
@aha_1980 the output is in red, which I think means it knows it is an error.
Here is a sample:
19:31:18: Running steps for project helloworld... 19:31:18: Starting: "/usr/bin/ninja" 3>&1 1>&2 2>&3 [1/3] Generating version.h with a custom command. [2/3] Compiling C object 'helloworld_debug@exe/src_main.c.o'. FAILED: helloworld_debug@exe/src_main.c.o <snip> badcode; ^~~~~~~ ../../src/main.c:85:5: note: each undeclared identifier is reported only once for each function it appears in ninja: build stopped: subcommand failed. 19:31:19: The process "/usr/bin/ninja" exited with code 1. Error while building/deploying project helloworld (kit: ARM Bare Metal) The kit ARM Bare Metal has configuration issues which might be the root cause for this problem. When executing step "Custom Process Step" 19:31:19: Elapsed time: 00:01.
Looking more closely at the output, I see that it clearly says "The kit ARM Bare Metal has configuration issues which might be the root cause for this problem."
I hadn't configured the compiler in the Kits section of the options.
Having set the compiler correctly, it is now parsing the output! I should have spotted that earlier.
Thanks for the assistance.