#5845 - SimonB - Fri May 09, 2003 10:07 pm
Kevin Weatherman sent us an email earlier this week:
I made this utility here to fix some problems with inegrating the ARM ADS (the ARM development system) with Microsoft Developer Studio. You've seen similar things for GCC. It brings back the double click on error/warning lines. Plus I added a filter to filter out some warning messages that you can't control with the tools them selves.
some more info from the readme:
This program is a small utility to fix some of the problems integrating the
"ARM(R) ADS v1.2" (ARM Developer Suite), with "Microsoft Visual Studio v6".
What it does:
1. Restores line number info in the proper syntax so you can double click
on the warning or error in the output window and it will jump you to
the offending file (just like you can when you are working with Windows
executables).
2. Filters out unwanted compiler, assembler, and linker warning messages.
This is necessary because the ADS doesn't have the proper support to filter
out individual messages that it spews out so profusely.
The filters are hardcoded into the exectuable (ADSMSGFIX.EXE), you'll have to
recompile the source to make changes.
Also refer to the ADS documentation as there is some control over messages
that one might be able to do from the command line before adding them to the
filter lists.
get it here [35kb]
I made this utility here to fix some problems with inegrating the ARM ADS (the ARM development system) with Microsoft Developer Studio. You've seen similar things for GCC. It brings back the double click on error/warning lines. Plus I added a filter to filter out some warning messages that you can't control with the tools them selves.
some more info from the readme:
This program is a small utility to fix some of the problems integrating the
"ARM(R) ADS v1.2" (ARM Developer Suite), with "Microsoft Visual Studio v6".
What it does:
1. Restores line number info in the proper syntax so you can double click
on the warning or error in the output window and it will jump you to
the offending file (just like you can when you are working with Windows
executables).
2. Filters out unwanted compiler, assembler, and linker warning messages.
This is necessary because the ADS doesn't have the proper support to filter
out individual messages that it spews out so profusely.
The filters are hardcoded into the exectuable (ADSMSGFIX.EXE), you'll have to
recompile the source to make changes.
Also refer to the ADS documentation as there is some control over messages
that one might be able to do from the command line before adding them to the
filter lists.
get it here [35kb]