It would seem I spoke to soon about the messages formatting correctly.  The message I saw that was correctly formatted was generated by VS, not the Keil toolchain.  I tinkered with the BuildMessageRegexes.xml file a bit.  If I remove the <GCCDetailedMessage> line, it will build successfully.  However, it still does not format the compiler messages correctly.  It does not seem to matter how the RegEx is written, it always formats the same.  It appears to be ignoring the RegEx defined in the BuildMessageRegexes.xml file.  I validated the modified RegEx against the build output in RegExBuddy and it matches.  What am I missing?

• This reply was modified 8 years, 2 months ago by mmoore.

Thanks for the update.  This has resolved the issue where the project won’t build with   <BuildMessageTemplateFile>BuildMessageRegexes.xml</BuildMessageTemplateFile> defined in the .vgdbsettings file.  However, I am still getting incorrectly formatted compiler errors and the changes I make to the RegEx in BuildMessageRegexes.xml appear to make no difference.  I have tested my RegEx against the build output in RegexBuddy and it matches as expected.  Here is the RegEx for compiler messages:

<GCCMessage>^1>”(.*)”, line ([0-9]+) : (error|warning) : (.*)$</GCCMessage>

I thought perhaps XML did not like the angle bracket, so I have also tried:

<GCCMessage>^1<![CDATA[>]]>”(.*)”, line ([0-9]+) : (error|warning) : (.*)$</GCCMessage>

and

<GCCMessage>”(.*)”, line ([0-9]+) : (error|warning) : (.*)$</GCCMessage>

as well as several other permutations.  I am attempting to match compiler messages in build output like this:

1>”../application/some_file.c”, line 424 : warning : #177-D: function “naughty_function”  was declared but never referenced

The error list is always formatted as “#177-D: function “naughty_function”  was declared but never referenced” with blank file and line 1.  Please let me know what I need to do differently to make this work.

Thanks for your response.  I have ensured that the .vgdbsettings and BuildMessageRegexes.xml files are configured as you indicated.  I modified the Makefile like so:

ifeq ($(TARGETTYPE),APP)
ROM_SECTION_NAME := ER_IROM1
$(BINARYDIR)/$(TARGETNAME): $(all_objs) $(EXTERNAL_LIBS)
$(LD) -o $(@:.elf=.axf) $(LDFLAGS) $(START_GROUP) $(all_objs) $(LIBRARY_LDFLAGS) $(END_GROUP)
@echo "../../LEDBlink.cpp", line 10 : warning : #177-D: function "naughty_function" was declared but never referenced
@echo "../application/source_file.c", line 71 : warning : #177-D: variable "_naughty_variable" was declared but never referenced
@echo "../application/source_file.c", line 71 : warn : #177-D: variable "_naughty_variable" was declared but never referenced
$(FROMELF) --bin --output $(@:.elf=.bin) $(@:.elf=.axf)
$(OBJCOPY) --remove-section $(ROM_SECTION_NAME) \
--add-section $(ROM_SECTION_NAME)=$(@:.elf=.bin) \
--set-section-flags \
$(ROM_SECTION_NAME)=CONTENTS,ALLOC,LOAD,READONLY,CODE \
--change-section-address $(ROM_SECTION_NAME)=0x00029000 \
$(@:.elf=.axf) $@
endif

I added three echo lines to the Makefile.  The first is per your listing above.  The second is a verbatim copy of the build output.  The third is a copy of the build output with ‘warn’ instead of ‘warning’ to test the RegEx match.  These all format in the build output as expected.  However, the compiler output is still not formatted.  Here is a relevant section of the build output:

1>C:/Keil_v5/ARM/ARMCC/bin/armcc.exe -g -O0 --c99 --gnu ... -o Debug/app_nvm_settings.o
1>"../application/source_file.c", line 71 : warning : #177-D: variable "_naughty_variable" was declared but never referenced
1> static some_type_t _naughty_variable;
1> ^
1>"../application/source_file.c", line 424 : warning : #177-D: function "naughty_function" was declared but never referenced
1> static void naughty_function(void)
1> ^
1>../application/source_file.c: 2 warnings, 0 errors
1>C:/Keil_v5/ARM/ARMCC/bin/armcc.exe -g -O0 --c99 --gnu ... -o Debug/source_file_2.o
1>C:/Keil_v5/ARM/ARMCC/bin/armcc.exe -g -O0 --c99 --gnu ... -o Debug/source_file.o
1>Program Size: Code=39920 RO-data=1780 RW-data=436 ZI-data=8420
1>C:/SysGCC/arm-eabi/bin/arm-eabi-objcopy.exe: Debug/target.axf: warning: Empty loadable segment detected, is this intentional ?
1>C:/SysGCC/arm-eabi/bin/arm-eabi-objcopy.exe: Debug/target.elf: warning: allocated section 'RW_IRAM1' not in segment
1>C:/SysGCC/arm-eabi/bin/arm-eabi-objcopy.exe: Debug/target.elf: warning: allocated section 'ER_IROM1' not in segment
1>C:/Keil_v5/ARM/ARMCC/bin/armcc.exe -g -O0 --c99 --gnu ... -o Debug/source_file_3.o
1>C:/Keil_v5/ARM/ARMCC/bin/armlink.exe -o Debug/target.axf ...
1>C:\development\the\path\to\the\project\visual_gdb\..\..\LEDBlink.cpp(10): warning : #177-D: function "naughty_function" was declared but never referenced
1>C:\development\the\path\to\the\project\visual_gdb\..\application\ source_file.c(71): warning : #177-D: variable "_naughty_variable" was declared but never referenced
1>"../application/source_file.c", line 71 : warn : #177-D: variable "_naughty_variable" was declared but never referenced

I also tried removing the end-of-line anchor from the RegEx, but the results were the same.  Have you tested this with your demo project from the Keil toolchain tutorial under VS 2017?  Is the Keil toolchain output somehow bypassing the RegEx filtering? Please let me know what I can do or if there is anything I can provide to get this resolved.  Thanks!

• This reply was modified 8 years, 1 month ago by mmoore.
• This reply was modified 8 years, 1 month ago by mmoore.

I finally got it figured out. Apparently the output was already being re-written by the time that it showed up incorrectly formatted in the build output. So the line that I have been trying to match (per the previous post):

"../application/source_file.c", line 71 : warning : #177-D: variable "_naughty_variable" was declared but never referenced

actually comes out of the compiler looking like this:

"../application/source_file.c", line 71: Warning: #177-D: variable "_naughty_variable" was declared but never referenced

So apparently the capitalization of warning/error was different, as well as the spacing before the colon. I modified the RegEx and the compiler messages are now formatted correctly. Thanks for all your help.

• This reply was modified 8 years, 1 month ago by mmoore.