1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-08-16 20:55:44 +02:00

bug 289168: Updated cross-references in the doc related to error parsers

This commit is contained in:
Andrew Gvozdev 2010-06-02 22:03:41 +00:00
parent 738da44d29
commit 18b2a05a56
7 changed files with 68 additions and 24 deletions

View file

@ -13,7 +13,10 @@
<h1>Makefile Project - Error Parsers page </h1>
<p>Use the <strong>Error Parsers</strong> page in the <img src="../images/command_link.png" border="0" alt="" > <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.cdt.managedbuilder.ui.preferences.PrefPage_NewCDTProject)")'>Makefile Projects</a> preference panel to view a list of the filters that detect error patterns in the build output log.</p>
<p>Use the <strong>Error Parsers</strong> page in the <img src="../images/command_link.png" border="0" alt="" >
<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.cdt.managedbuilder.ui.preferences.PrefPage_NewCDTProject)")'>
Makefile Projects</a> preference panel to define a list of error parsers that will be assigned to a new <strong>Makefile Project</strong>
created by a New CDT Project Wizard.</p>
<p><img src="../images/new_make-error_parser.png" alt="Make Error Parser Preferences Dialog Box" width="540" height="516"></p>
<table width="600px" cellpadding="5" cellspacing="0" border="1" fgcolor="DDD" >
@ -53,14 +56,22 @@
</tr>
</tbody>
</table>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>
<a href="../concepts/cdt_c_build_over.htm">Build overview</a></p>
<br><a href="../concepts/cdt_c_build_over.htm">Build overview</a>
</p>
<p><img border="0" src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br>
<a href="../tasks/cdt_t_proj_error_parser.htm">Tuning Error Parsers</a></p>
<p><img border="0" src="../images/ngref.gif" ALT="Related reference" width="143" height="21"> <br>
<a href="cdt_o_proj_prop_pages.htm">New CDT Project Wizard</a></p>
<br><a href="../tasks/cdt_o_builderrors.htm">Tracking down compilation errors</a>
<br><a href="../tasks/cdt_t_proj_error_parser.htm">Tuning Error Parsers</a>
</p>
<p><img border="0" src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br><a href="cdt_o_proj_prop_pages.htm">New CDT Project Wizard</a>
<br><a href="../reference/cdt_u_console_view.htm">Console View</a>
<br><a href="../reference/cdt_u_problems_view.htm">Problems View</a>
</p>
<hr>
<img src="../images/ng00_04a.gif" ALT="IBM Copyright Statement" > <br>
<img src="../images/nokiaCopyright.png" alt="Nokia Copyright Statement" width="375" height="12">

View file

@ -54,14 +54,21 @@
</table>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>
<a href="../concepts/cdt_c_build_over.htm">Build overview</a></p>
<br><a href="../concepts/cdt_c_build_over.htm">Build overview</a></p>
</p>
<p><img border="0" src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br>
<a href="../tasks/cdt_t_proj_build_set.htm">Defining Project Build settings</a><br>
<a href="../tasks/cdt_o_build_task.htm">Building projects</a></p>
<p><img border="0" src="../images/ngref.gif" ALT="Related reference" width="143" height="21"> <br>
<a href="../reference/cdt_o_views.htm">Views</a></p>
<br><a href="../tasks/cdt_o_builderrors.htm">Tracking down compilation errors</a>
<br><a href="../tasks/cdt_t_proj_build_set.htm">Defining Project Build settings</a>
<br><a href="../tasks/cdt_o_build_task.htm">Building projects</a>
</p>
<p><img border="0" src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br><a href="../reference/cdt_u_prop_build_settings_errparser.htm">Error Parsers tab</a>
<br><a href="../reference/cdt_u_console_view.htm">Console View</a>
<br><a href="../reference/cdt_u_problems_view.htm">Problems View</a>
</p>
<hr>
<img src="../images/ng00_04a.gif" ALT="IBM Copyright Statement" ><br>
<img src="../images/nokiaCopyright.png" ALT="Nokia Copyright Statement" >

View file

@ -8,7 +8,7 @@
</head>
<body>
<h1>C/C++ Project Properties, Build, Settings, Error Parsers</h1>
<p>Use the <strong>Error Parsers</strong> properties tab to customize the list of filters that detect error patterns in the
<p>Use the <strong>Error Parsers</strong> properties tab to customize the list of parsers that detect error messages in the
build output log.</p>
<p><img img="" src="../images/prop_error.png"
alt="C/C++ Project Properties, Build, Settings, Error Parsers"></p>
@ -63,8 +63,9 @@ build output log.</p>
<p><img border="0" src="../images/ngtasks.gif" alt="Related tasks"
width="143" height="21">
<br>
<a href="../tasks/cdt_t_proj_error_parser.htm">Tuning Error Parsers</a></p>
<br><a href="../tasks/cdt_t_proj_error_parser.htm">Tuning Error Parsers</a>
<br><a href="../tasks/cdt_o_builderrors.htm">Tracking down compilation errors</a>
</p>
<p style="margin-top: 0pt; margin-bottom: 0pt;"><img border="0"
src="../images/ngref.gif" alt="Related reference" width="143"

View file

@ -15,6 +15,8 @@
<p>After a build finishes, CDT displays the build output in the Console View. The build output shows
the result of build and a user can inspect it to find out if it was successful or not. To assist with that
CDT Error Parsers scan build output and create Problem Markers which are presented in a variety of ways:
</p>
<p>
<ul>
<li>as highlighted lines on the console,</li>
<li>in the Problems View,</li>
@ -22,13 +24,34 @@ CDT Error Parsers scan build output and create Problem Markers which are present
<li>icons in editor's overview rulers,</li>
<li>as squiggly line marking the problematic code in editor.</li>
</ul>
There are 3 types of Problem Markers: Errors, Warnings and Info. A user can control how the markers are
</p>
<p>
There are 3 types of Problem Markers: Errors <img src="../images/icon_error.gif" alt="Error">,
Warnings <img src="../images/icon_warning.gif" alt="Warning"> and Info<img src="../images/icon_info.gif" alt="Info">.
A user can control how the markers are
generated on "Error Parsers" Preference page.
</p>
<p>The following topics describe how to view and manage compile errors.</p>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_jumperror.htm">Jumping to errors</a><br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_filtererror.htm">Filtering the Problems view</a><br>
<p>The following topics describe how to view and manage compile errors:
<br><img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_jumperror.htm">Jumping to errors</a>
<br><img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_filtererror.htm">Filtering the Problems view</a>
</p>
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br><a href="../concepts/cdt_c_build_over.htm">Build overview</a></p>
</p>
<p><img border="0" src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br><a href="../tasks/cdt_t_proj_error_parser.htm">Tuning Error Parsers</a>
<br><a href="../tasks/cdt_t_proj_build_set.htm">Defining Project Build settings</a>
<br><a href="../tasks/cdt_o_build_task.htm">Building projects</a>
</p>
<p><img border="0" src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br><a href="../reference/cdt_u_prop_build_settings_errparser.htm">Error Parsers tab</a>
<br><a href="../reference/cdt_u_console_view.htm">Console View</a>
<br><a href="../reference/cdt_u_problems_view.htm">Problems View</a>
</p>
<p><img src="../images/ng00_04a.gif" ALT="QNX Copyright Statement" ></p>

View file

@ -20,7 +20,7 @@
<ol>
<li>In Problems view, click the <strong>View Menu</strong> icon
<img border="0" src="../images/icon_menu.png" width="23" height="21" alt="View Menu icon">
<img border="0" src="../images/icon_menu.png" align="center" alt="View Menu icon">
in the top right corner of the view.</li>
<li>Use <strong>Configure Contents...</strong> to define your custom filter and click <strong>OK</strong>.</li>
<li>In <strong>View Menu</strong> select <strong>Show</strong> and then your filter.</li>
@ -34,6 +34,7 @@
<p><img border="0" src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br><a href="cdt_o_builderrors.htm">Tracking down compilation errors</a>
<br><a href="../tasks/cdt_t_proj_error_parser.htm">Tuning Error Parsers</a>
</p>
<p><img border="0" src="../images/ngref.gif" ALT="Related reference" width="143" height="21">

View file

@ -44,6 +44,7 @@ Informational messages are marked with Info <img src="../images/icon_info.gif" a
<p><img border="0" src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br><a href="cdt_o_builderrors.htm">Tracking down compilation errors</a>
<br><a href="../tasks/cdt_t_proj_error_parser.htm">Tuning Error Parsers</a>
</p>
<p><img border="0" src="../images/ngref.gif" ALT="Related reference" width="143" height="21">

View file

@ -77,14 +77,14 @@ Note that that kind of parser needs to be the first to be able to provide the CW
<p><img border="0" src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br><a href="cdt_o_builderrors.htm">Tracking down compilation errors</a>
<br><a href="../tasks/cdt_t_proj_error_parser.htm">Tuning Error Parsers</a>
</p>
<p><img border="0" src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br><a href="../reference/cdt_u_console_view.htm">Console View</a>
<br><a href="../reference/cdt_u_problems_view.htm">Problems View</a>
<br><a href="../reference/cdt_u_pref_build.htm">Build preferences</a>
<br><a href="../reference/cdt_u_prop_build_settings_errparser.htm">Error Parsers tab</a>
<br><a href="../reference/cdt_u_pref_build_error_parsers.htm">Error Parser Options</a>
<br><a href="../reference/cdt_u_newproj_parser_error.htm">Error Parsers, C/C++ Properties</a>
</p>
<img src="../images/ng00_04a.gif" ALT="QNX Copyright Statement" >