1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-04-23 14:42:11 +02:00

Bug 202803 - Updates to user doc.

This commit is contained in:
Doug Schaefer 2007-09-21 01:56:25 +00:00
parent 853d98c8dd
commit fbc074aabc
52 changed files with 1277 additions and 573 deletions

View file

@ -0,0 +1,52 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Views in the C/C++ perspective</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<h1>Discovery options</h1>
<p>For projects where the IDE generates a makefile to build the project automatically, the IDE has more information about the internal build state of the make project compared to those projects where you provide a makefile to build the project.
<p>For example, a makefile includes build information and other settings, such as include file paths (-I) and macro definitions (-D), which are standard to the build tools (such as the compiler and linker). When the makefile is automatically created for you, this information is known to Eclipse to a greater extent then when you create and manage the makefile for a project yourself. The type of information affects the search capabilities and Code Assist abilities of Eclipse. Therefore, in this example, the purpose of Discovery Options is for improved search and Code Assist capability for projects where Eclipse does not manage the makefile for you. For example, in an open source file of an editor view, to see the declaration for a function that the code calls, you select the function, right click, and select <b>Open Declaration</b> from the context menu. If the location of the include file (that was coded in the makefile for the project) containing the function declaration was in some directory, the CDT would not find the declaration because it has no visibility for that include path. Consequently, you can use Discovery Options in the CDT to enhance the IDE build state by parsing the build process output to extract build path information that the CDT searching mechanism uses to locate and open the include file. By default, the CDT uses GNU* tools (gcc, etc.). If you want to build your projects using another compiler, use the settings described here.</p>
<p>Scanner configuration discovery is tightly linked to project's build process. The first part of scanner discovery begins during the make build for make projects where you provide the makefile. The Eclipse CDT parses the build output for compiler commands with options that specify the definition of the preprocessor symbols and include search paths (for the gcc compiler, -D and -I), and then it stores the information as the project's discovered scanner configuration.
<p>Next, after the build process completes, it is implemented as a separate Eclipse builder where it runs a generate scanner info command, and then parses the output (properties specified on the Discover Options tab for Builds in the Project Properties window).
<p>For C++, the default generate scanner information command is <b>gcc -E -P -v myfile.c | myfile.cpp</b>. This command reads the compiler's configuration file and prints the information that includes compiler's internally defined preprocessor symbols and include search paths.
<p>A single scanner configuration is applicable to all the files in a project. Although Eclipse discovers the information for each compilation unit, it stores the scanner configuration on a per project basis. This means that Eclipse applies a single, cumulative scanner configuration to all files in a project.
<p>The following situations identify circumstances when certain parts of the scanner configuration are in conflict:
<ul>
<li>Symbol definitions that contradict
<li>An incorrect order for the include paths
<li>Internal scanner information may not be applicable to all the files in a project (for a single compiler), because some files might be compiled with a different compiler, or have target specific options specified.
</ul>
</p>
<p><b>Note:</b> Only basic command line options are supported. In addition, only basic scanner configuration related command line options are recognized (for example, -D and -I for gcc). For some of the commands, their relative position in the command line is important. For information about these options, see the documentation for the utilities you are using.
<p><img border="0" src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br><a href="cdt_c_over_cdt.htm">CDT Overview</a>
<br><a href="cdt_c_perspectives.htm">C/C++ perspectives</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>
<p>
<img src="../images/rh03_04.gif" ALT="Red Hat Copyright Statement"><br>
<img src="../images/ng00_07.gif" ALT=" IBM Copyright Statement" >
</p>
</body>
</html>

Binary file not shown.

After

Width:  |  Height:  |  Size: 9 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.9 KiB

After

Width:  |  Height:  |  Size: 4.8 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 36 KiB

After

Width:  |  Height:  |  Size: 44 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 41 KiB

After

Width:  |  Height:  |  Size: 32 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 38 KiB

After

Width:  |  Height:  |  Size: 42 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 54 KiB

After

Width:  |  Height:  |  Size: 43 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 65 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 32 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 49 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 21 KiB

After

Width:  |  Height:  |  Size: 43 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 46 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 41 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 8 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 9.2 KiB

After

Width:  |  Height:  |  Size: 20 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 25 KiB

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 22 KiB

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 63 KiB

After

Width:  |  Height:  |  Size: 53 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 55 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 24 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 28 KiB

After

Width:  |  Height:  |  Size: 34 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 12 KiB

After

Width:  |  Height:  |  Size: 28 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 12 KiB

After

Width:  |  Height:  |  Size: 24 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 31 KiB

After

Width:  |  Height:  |  Size: 46 KiB

View file

@ -1,43 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Project properties</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<h1>Managed Make Project preferences, Environment</h1>
<p style="margin-top: 0">Customizes the build environment for all managed make projects in the workspace.</p>
<p style="margin-top: 0">
<img border="0" src="../images/mpref_env.png" width="580" height="525"></p>
<p>You can add, remove and edit build process environment variables to be used for all managed make
projects in the workspace.&nbsp; Two tables are displayed - one for user-defined environment variables
and one for non user-defined environment
variables.&nbsp;Each
table contains two columns<b>:</b></p>
<p><b>Name</b> of the environment variable</p>
<p><b>Value </b>of the environment variable.</p>
<p>You can view all environment variables that are not user-defined in the <b>System
Variables</b> table.&nbsp;</p>
<p class="MsoNormal">You can view all user-defined variables in the <b>User
Variables</b> table.&nbsp;&nbsp;
A user-defined variable overrides a non user-defined variable of the same
name.&nbsp; Overridden variables are displayed in bold in
the <b>System Variables</b> table.</p>
<p class="MsoNormal">For more detailed information about the managed make Environment
settings, see the description in the <a href="cdt_u_mprop_env.htm">Build Environment Property Pages</a>.</p>
<p class="MsoNormal" style="margin-top: 0; margin-bottom: 0"><img border="0" src="../images/ngref.gif" ALT="Related reference" width="143" height="21"></p>
<p style="margin-top: 0; margin-bottom:0"><a href="cdt_u_mprop_env.htm">C/C++
Project Properties, Managed, C/C++ Build, Environment</a></p>
<p style="margin-top: 0; margin-bottom:0"><a href="cdt_u_mprop_macros.htm">C/C++
Project Properties, Managed, C/C++ Build, Build Macros</a></p>
<p style="margin-top: 0; margin-bottom:0"><a href="cdt_o_mproj_pref_macro.htm">
Managed Build Project preferences, Macros</a></p>
<p><img src="../images/intl_05.gif" ALT="Intel Copyright Statement" ></p>
</body>
</html>

View file

@ -18,24 +18,79 @@ of a C/C++ project's properties window.<br>
alt="C/C++ File Properties, Discovery Options"
><br>
</p>
<dl>
<dt>Left pane (list)</dt>
<dd>Language related to given file is displayed here.
</dd>
<dt>Automate scanner configuration discovery</dt>
<dd>Select this checkbox to configure the automatic discovery of
paths and symbols. When unchecked, all controls below became disabled.</dd>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Discovery options</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Exclude resource from build</dt></td>
<td>Excludes the selected file from the build process.</td>
</tr>
<tr>
<td>Left pane list (language specific)</td>
<td>Shows a list of language specific compilers. Select a language from the list.</td>
</tr>
<tr>
<td><dt>Automate discovery of paths and symbols</dt></td>
<td>Scans the build output to populate the path and symbol tables, such as symbol definitions, system include directories, local include directories, macros files, and include files. If this option is not selected, the <b>Discovery profile options</b> below do not appear.</td>
</tr>
<tr>
<td><dt>Report path detection problems</dt></td>
<td>Sets the notification of diagnostic errors for include paths that the Eclipse CDT is unable to resolve as it parses the build output.</td>
</tr>
<tr>
<td><dt>Discovery profile options</dt></td>
<td>Indicates the discovery profile to use for paths and symbol detection. The type of <b>Configuration</b> and <b>Discovery Profile Scope</b> you specify determine what which <b>Discovery Profile</b> options display on this tab. This set of controls is profile-specific. It may vary from one profile to another.</td>
</tr>
<tr>
<td><dt>Enable generate scanner info command</dt></td>
<td>Enables the retrieval of information from the scanner. If it is not selected, the includes will be populated with default gcc system includes; Eclipse gathers the compiler settings based on the specified toolchain. This means that the Eclipse CDT can obtain the default gcc system includes to associate with the project.
<p>When selected, you can specify any required compiler specific commands in the <b>Compiler invocation command</b> field.</p>
</td>
</tr>
<tr>
<td><dt>Compiler invocation command</dt></td>
<td>Indicates the compiler specific command used to invoke the compiler (such as <tt>gcc</tt>, or more complicated commands used to perform all necessary steps for compiling C/C++ source files into .o files, and linking the object files and libraries into an executable program. For example, the command <b>gcc -E -P -v hello.c | hello.cpp</b> reads a compiler's configuration file and prints out information that includes the compiler's internally defined preprocessor symbols and include search paths. The information is complementary to the scanner configuration discovered when the output is parsed (if you've enabled the <b>Enable build output scanner info discovery</b> option), and is added to the project's scanner configuration. You can click <b>Browse</b> to locate this command, if required.
<p><b>Note:</b> The parsing of build output for scanner information is compiler specific. For example, the GNU toolchain compilers (gcc and g++) use -I for include paths, and -D for symbol definitions. Consult your compiler specific documentation for more information about scanner information commands, such as the following gcc commands:</p>
<ul>
<li><samp>-D <span style="font-style: italic;">name</span></samp></li>
<li><samp>-I</samp></li>
<li><samp>-U <span style="font-style: italic;">name</span></samp></li>
<li><samp>-I-</samp></li>
<li><samp>-nostdinc</samp></li>
<li><samp>-nostdinc++</samp></li>
<li><samp>-include <span style="font-style: italic;">file</span></samp></li>
<li><samp>-imacros <span style="font-style: italic;">file</span></samp></li>
<li><samp>-idirafter <span style="font-style: italic;">dir</span></samp></li>
<li><samp>-isystem <span style="font-style: italic;">dir</span></samp></li>
<li><samp>-iprefix <span style="font-style: italic;">prefix</span></samp></li>
<li><samp>-iwithprefix <span style="font-style: italic;">dir</span></samp></li>
<li><samp>-iwithprefixbefore <span style="font-style: italic;">dir</span></samp></li>
</ul>
</td>
</tr>
<tr>
<td><dt>Browse</dt></td>
<td>Click to browse for a file to include in the compiler invocation command. This button is only visible when <b>Configuration</b> is set to Release and the <b>Discovery Profiles Scope</b> is set to <b>Configuration-wide</b>.</td>
</tr>
</tbody>
</table>
<dt>Report path detection problems</dt>
<dd>Enables or disables corresponding diagnostic messages.</dd>
<dt>Discovery profile</dt>
<dd>Select discovery profile from list.</dd>
<dt>Discovery profile options</dt>
<dd>This set of controls is profile-specific. It may vary from one profile to another.</dd>
</dl>
<p><img src="../images/ngref.gif" alt="Related reference" border="0"
height="21" width="143"><br>
@ -53,16 +108,16 @@ paths and symbols. When unchecked, all controls below became disabled.</dd>
</ul>
<li>C/C++ General</li>
<ul>
<li><a href="cdt_u_fileprop_lang_mapp.htm">Language Mappings</a>
<li>Paths and Symbols</li>
<ul>
<li><a href="cdt_u_fileprop_inc.htm">Includes tab</a>
<li><a href="cdt_u_fileprop_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_pns_hier.htm">Data Hierarchy tab</a>
</ul>
</ul>
<li><a href="cdt_u_prop_rundebug.htm">Run/Debug Settings page</a>
</ul>
</p>
<p><img src="../images/intl_07.gif" ALT="Intel Copyright Statement" ></p>
</body>

View file

@ -0,0 +1,54 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Language Mappings preferences</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<h1>Language Mappings preferences</h1>
<p>Customize the use of C/C++ language associations for the workspace. </p>
<p><img src="../images/fileprop_language_mappings.png" width="790" height="451"></p>
<table cellpadding="5" cellspacing="0" border="1" >
<caption>
<b>Language Mappings Options</b>
</caption>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td width="171" valign="top"><b>Content Type </b></td>
<td width="503" valign="top">The content type associated with the language. </td>
</tr>
<tr>
<td valign="top"><b>Configuration</b></td>
<td valign="top">Shows the list of configurations for the selected content type. </td>
</tr>
<tr>
<td valign="top"><b>Language</b></td>
<td valign="top">Shows the list of corresponding languages associated with the configurations in the list for the specific content type. </td>
</tr>
</tbody>
</table>
<p><img border="0" src="../images/ngref.gif" alt="Related reference"
width="143" height="21"><br>
<ul>
<li>Project Properties, C/C++ General category - <a href="cdt_u_prop_general_lng.htm">Language Mapping page</a>
<li>File Properties, C/C++ General category - <a href="cdt_u_fileprop_lng.htm">Language Mapping page</a>
</ul>
</p>
<p><img src="../images/nokia2007Copyright.png" width="255" height="14"></p>
</body>
</html>

View file

@ -3,50 +3,102 @@
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>C/C++ File Properties, Build, Settings, Tool Settings tab </title>
<title>C/C++ File Properties, Build, Settings, Tool settings tab </title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<h1>C/C++ File Properties, Build, Settings, Tool Settings tab</h1>
<h1>C/C++ File Properties, Build, Settings, Tool settings tab</h1>
Customizes the tools and tool options used in your build configuration.
<p><img img="" src="../images/cdt_file_toolsett.png"
alt="C/C++ File Properties, Build, Settings, Tool Settings tab"></p>
<p></p>
<dl>
<dt>Left pane:</dt>
<dd>Displays list of tools and their option categories. Select required line to edit its options.</dd>
<dt>Right pane:</dt>
<dd>List of options for selected tool or category.
</dd>
<dt><br>Available for :</dt>
<dd>CDT projects, folders and source files</dd>
</dl>
<p><img border="0" src="../images/ngref.gif" alt="Related reference"
width="143" height="21"><br>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Tool Settings options</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td>(Left pane)</td>
<td>Displays a list of tools and their option categories. Select a desired tool from the list to modify its options.</tr>
<tr>
<td>(Right pane)</td>
<td>Displays the options that you can modify for the selected tool. This list of options changes depending on which options category you select for a specific tool in the left pane.</td>
</tr>
</tbody>
</table>
<br>
<p><b>Available for:</b> CDT source files</p>
<p style="margin-top: 0pt; margin-bottom: 0pt;"><img border="0"
src="../images/ngref.gif" alt="Related reference" width="143"
height="21"><br>
<ul>
<li><a href=cdt_u_fprop_resource.htm>Resource</a></li>
<li>C/C++ Build</li>
<ul>
<li><a href=cdt_u_fileprop_discovery.htm>Discovery options</a></li>
<li>Settings</li>
<ul>
<li><a href=cdt_u_fileprop_toolsettings.htm>Tool chains setting tab</a></li>
<li><a href=cdt_u_fileprop_steps.htm>Build Steps tab</a></li>
</ul>
<li><a href="cdt_u_prop_build_toolchain.htm">Tool chain editor page</a>
</ul>
<li>C/C++ General</li>
<ul>
<li>Paths and Symbols</li>
<ul>
<li><a href="cdt_u_fileprop_inc.htm">Includes tab</a>
<li><a href="cdt_u_fileprop_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_resource.htm">Project Properties, Resource page</a>
<li><a href="cdt_u_prop_builders.htm">Project Properties, Builders page</a>
<li><a href="cdt_u_prop_all.htm">Project Properties, common C/C++ Configurations handling</a>
<ul type="disc">
<li><a href="cdt_u_prop_manage_dialog.htm">Manage Configurations dialog</a>
<li><a href="cdt_u_prop_manage_newdialog.htm">Create Configuration dialog</a>
<li><a href="cdt_u_prop_manage_rendialog.htm">Rename Configuration dialog</a>
</ul>
<li><a href="cdt_u_prop_build.htm">Project Properties, C/C++ Build category</a>
<ul type="disc">
<li><a href="cdt_u_prop_build_discovery.htm">Discovery options page</a>
<li><a href="cdt_u_prop_build_environment.htm">Environment page</a>
<li>Settings page
<ul>
<li><a href="cdt_u_prop_build_settings_tool.htm"> Tool Settings tab</a>
<li><a href="cdt_u_prop_build_settings_steps.htm"> Build Steps tab</a>
<li><a href="cdt_u_prop_build_settings_artifact.htm"> Build Artifact tab</a>
<li><a href="cdt_u_prop_build_settings_binparser.htm">Binary Parsers tab</a>
<li><a href="cdt_u_prop_build_settings_errparser.htm">Error Parsers tab</a>
</ul>
<li><a href="cdt_u_prop_build_toolchain.htm">Tool chain editor page</a>
<li><a href="cdt_u_prop_build_variables.htm">Variables page</a>
</ul>
<li>Project Properties, C/C++ General category
<ul type="disc">
<li><a href="cdt_u_prop_general_doc.htm">Documentation page</a>
<li><a href="cdt_u_prop_general_exp.htm">Export Settings page</a>
<!--ul>
<li><a href="cdt_u_prop_general_exp_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_exp_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_exp_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_exp_libpath.htm">Libraries path tab</a>
</ul-->
<li><a href="cdt_u_prop_general_typ.htm">File Types page</a>
<li><a href="cdt_u_prop_general_idx.htm">Indexer page</a>
<li><a href="cdt_u_prop_general_lng.htm">Language Mapping page</a>
<li>Paths and Symbols page
<ul>
<li><a href="cdt_u_prop_general_pns_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_pns_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_pns_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_pns_libpath.htm">Libraries path tab</a>
<li><a href="cdt_u_prop_general_pns_src.htm">Source Location tab</a>
<li><a href="cdt_u_prop_general_pns_out.htm">Output Location tab</a>
<li><a href="cdt_u_prop_general_pns_ref.htm">References tab</a>
<li><a href="cdt_u_prop_general_pns_hier.htm">Data Hierarchy tab</a>
</ul>
</ul>
<li><a href="cdt_u_prop_rundebug.htm">Run/Debug Settings page</a>
</ul>
</ul>
<li><a href="cdt_u_prop_ref.htm">C/C++ Project Properties, Project References page</a>
<li><a href="cdt_u_prop_rundebug.htm">C/C++ Project Properties, Run/Debug Settings page</a>
</ul>
</p>
<p><img src="../images/intl_07.gif" ALT="Intel Copyright Statement" ></p>

View file

@ -18,24 +18,79 @@ of a C/C++ project's properties window.<br>
alt="C/C++ Folder Properties, Discovery Options"
><br>
</p>
<dl>
<dt>Left pane (list)</dt>
<dd>Select required language here.
</dd>
<dt>Automate scanner configuration discovery</dt>
<dd>Select this checkbox to configure the automatic discovery of
paths and symbols. When unchecked, all controls below became disabled.</dd>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Discovery options</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Exclude resource from build</dt></td>
<td>Excludes the selected folder from the build process.</td>
</tr>
<tr>
<td>Left pane list (language specific)</td>
<td>Shows a list of language specific compilers. Select a language from the list.</td>
</tr>
<tr>
<td><dt>Automate discovery of paths and symbols</dt></td>
<td>Scans the build output to populate the path and symbol tables, such as symbol definitions, system include directories, local include directories, macros files, and include files. If this option is not selected, the <b>Discovery profile options</b> below do not appear.</td>
</tr>
<tr>
<td><dt>Report path detection problems</dt></td>
<td>Sets the notification of diagnostic errors for include paths that the Eclipse CDT is unable to resolve as it parses the build output.</td>
</tr>
<tr>
<td><dt>Discovery profile options</dt></td>
<td>Indicates the discovery profile to use for paths and symbol detection. The type of <b>Configuration</b> and <b>Discovery Profile Scope</b> you specify determine what which <b>Discovery Profile</b> options display on this tab. This set of controls is profile-specific. It may vary from one profile to another.</td>
</tr>
<tr>
<td><dt>Enable generate scanner info command</dt></td>
<td>Enables the retrieval of information from the scanner. If it is not selected, the includes will be populated with default gcc system includes; Eclipse gathers the compiler settings based on the specified toolchain. This means that the Eclipse CDT can obtain the default gcc system includes to associate with the project.
<p>When selected, you can specify any required compiler specific commands in the <b>Compiler invocation command</b> field.</p>
</td>
</tr>
<tr>
<td><dt>Compiler invocation command</dt></td>
<td>Indicates the compiler specific command used to invoke the compiler (such as <tt>gcc</tt>, or more complicated commands used to perform all necessary steps for compiling C/C++ source files into .o files, and linking the object files and libraries into an executable program. For example, the command <b>gcc -E -P -v hello.c | hello.cpp</b> reads a compiler's configuration file and prints out information that includes the compiler's internally defined preprocessor symbols and include search paths. The information is complementary to the scanner configuration discovered when the output is parsed (if you've enabled the <b>Enable build output scanner info discovery</b> option), and is added to the project's scanner configuration. You can click <b>Browse</b> to locate this command, if required.
<p><b>Note:</b> The parsing of build output for scanner information is compiler specific. For example, the GNU toolchain compilers (gcc and g++) use -I for include paths, and -D for symbol definitions. Consult your compiler specific documentation for more information about scanner information commands, such as the following gcc commands:</p>
<ul>
<li><samp>-D <span style="font-style: italic;">name</span></samp></li>
<li><samp>-I</samp></li>
<li><samp>-U <span style="font-style: italic;">name</span></samp></li>
<li><samp>-I-</samp></li>
<li><samp>-nostdinc</samp></li>
<li><samp>-nostdinc++</samp></li>
<li><samp>-include <span style="font-style: italic;">file</span></samp></li>
<li><samp>-imacros <span style="font-style: italic;">file</span></samp></li>
<li><samp>-idirafter <span style="font-style: italic;">dir</span></samp></li>
<li><samp>-isystem <span style="font-style: italic;">dir</span></samp></li>
<li><samp>-iprefix <span style="font-style: italic;">prefix</span></samp></li>
<li><samp>-iwithprefix <span style="font-style: italic;">dir</span></samp></li>
<li><samp>-iwithprefixbefore <span style="font-style: italic;">dir</span></samp></li>
</ul>
</td>
</tr>
<tr>
<td><dt>Browse</dt></td>
<td>Click to browse for a file to include in the compiler invocation command. This button is only visible when <b>Configuration</b> is set to Release and the <b>Discovery Profiles Scope</b> is set to <b>Configuration-wide</b>.</td>
</tr>
</tbody>
</table>
<dt>Report path detection problems</dt>
<dd>Enables or disables corresponding diagnostic messages.</dd>
<dt>Discovery profile</dt>
<dd>Select discovery profile from list.</dd>
<dt>Discovery profile options</dt>
<dd>This set of controls is profile-specific. It may vary from one profile to another.</dd>
</dl>
<p><img src="../images/ngref.gif" alt="Related reference" border="0"
height="21" width="143"><br>
@ -43,10 +98,11 @@ paths and symbols. When unchecked, all controls below became disabled.</dd>
<li><a href=cdt_u_fprop_resource.htm>Resource</a></li>
<li>C/C++ Build</li>
<ul>
<li><a href=cdt_u_fprop_discovery.htm>Discovery options</a></li>
<li><a href=cdt_u_fileprop_discovery.htm>Discovery options</a></li>
<li>Settings</li>
<ul>
<li><a href=cdt_u_fprop_toolsettings.htm>Tool chains setting tab</a></li>
<li><a href=cdt_u_fileprop_toolsettings.htm>Tool chains setting tab</a></li>
<li><a href=cdt_u_fileprop_steps.htm>Build Steps tab</a></li>
</ul>
<li><a href="cdt_u_prop_build_toolchain.htm">Tool chain editor page</a>
</ul>
@ -54,16 +110,13 @@ paths and symbols. When unchecked, all controls below became disabled.</dd>
<ul>
<li>Paths and Symbols</li>
<ul>
<li><a href="cdt_u_prop_general_pns_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_pns_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_pns_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_pns_libpath.htm">Libraries path tab</a>
<li><a href="cdt_u_prop_general_pns_hier.htm">Data Hierarchy tab</a>
<li><a href="cdt_u_fileprop_inc.htm">Includes tab</a>
<li><a href="cdt_u_fileprop_sym.htm">Symbols tab</a>
</ul>
</ul>
<li><a href="cdt_u_prop_rundebug.htm">Run/Debug Settings page</a>
</ul>
</p>
<p><img src="../images/intl_07.gif" ALT="Intel Copyright Statement" ></p>
</body>

View file

@ -7,47 +7,102 @@
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<h1>C/C++ Folder Properties, Build, Settings, Tool Settings tab</h1>
<h1>C/C++ Folder Properties, Build, Settings, Tool settings tab</h1>
Customizes the tools and tool options used in your build configuration.
<p><img img="" src="../images/cdt_fold_toolsett.png"
alt="C/C++ Folder Properties, Build, Settings, Tool Settings tab"></p>
alt="C/C++ Folder Properties, Build, Settings, Tool settings tab"></p>
<p></p>
<dl>
<dt>Left pane:</dt>
<dd>Displays list of tools and their option categories. Select required line to edit its options.</dd>
<dt>Right pane:</dt>
<dd>List of options for selected tool or category.
</dd>
<dt><br>Available for :</dt>
<dd>CDT projects, folders and source files</dd>
</dl>
<p><img border="0" src="../images/ngref.gif" alt="Related reference"
width="143" height="21"><br>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Tool settings options</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td>(Left pane)</td>
<td>Displays a list of tools and their option categories. Select a desired tool from the list to modify its options.</tr>
<tr>
<td>(Right pane)</td>
<td>Displays the options that you can modify for the selected tool. This list of options changes depending on which options category you select for a specific tool in the left pane.</td>
</tr>
</tbody>
</table>
<br>
<p><b>Available for:</b> CDT projects, folders and source files</p>
<p style="margin-top: 0pt; margin-bottom: 0pt;"><img border="0"
src="../images/ngref.gif" alt="Related reference" width="143"
height="21"><br>
<ul>
<li><a href=cdt_u_fprop_resource.htm>Resource</a></li>
<li>C/C++ Build</li>
<ul>
<li><a href=cdt_u_fprop_discovery.htm>Discovery options</a></li>
<li>Settings</li>
<ul>
<li><a href=cdt_u_fprop_toolsettings.htm>Tool chains setting tab</a></li>
</ul>
<li><a href="cdt_u_prop_build_toolchain.htm">Tool chain editor page</a>
</ul>
<li>C/C++ General</li>
<ul>
<li>Paths and Symbols</li>
<ul>
<li><a href="cdt_u_prop_resource.htm">Project Properties, Resource page</a>
<li><a href="cdt_u_prop_builders.htm">Project Properties, Builders page</a>
<li><a href="cdt_u_prop_all.htm">Project Properties, common C/C++ Configurations handling</a>
<ul type="disc">
<li><a href="cdt_u_prop_manage_dialog.htm">Manage Configurations dialog</a>
<li><a href="cdt_u_prop_manage_newdialog.htm">Create Configuration dialog</a>
<li><a href="cdt_u_prop_manage_rendialog.htm">Rename Configuration dialog</a>
</ul>
<li><a href="cdt_u_prop_build.htm">Project Properties, C/C++ Build category</a>
<ul type="disc">
<li><a href="cdt_u_prop_build_discovery.htm">Discovery options page</a>
<li><a href="cdt_u_prop_build_environment.htm">Environment page</a>
<li>Settings page
<ul>
<li><a href="cdt_u_prop_build_settings_tool.htm"> Tool Settings tab</a>
<li><a href="cdt_u_prop_build_settings_steps.htm"> Build Steps tab</a>
<li><a href="cdt_u_prop_build_settings_artifact.htm"> Build Artifact tab</a>
<li><a href="cdt_u_prop_build_settings_binparser.htm">Binary Parsers tab</a>
<li><a href="cdt_u_prop_build_settings_errparser.htm">Error Parsers tab</a>
</ul>
<li><a href="cdt_u_prop_build_toolchain.htm">Tool chain editor page</a>
<li><a href="cdt_u_prop_build_variables.htm">Variables page</a>
</ul>
<li>Project Properties, C/C++ General category
<ul type="disc">
<li><a href="cdt_u_prop_general_doc.htm">Documentation page</a>
<li><a href="cdt_u_prop_general_exp.htm">Export Settings page</a>
<!--ul>
<li><a href="cdt_u_prop_general_exp_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_exp_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_exp_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_exp_libpath.htm">Libraries path tab</a>
</ul-->
<li><a href="cdt_u_prop_general_typ.htm">File Types page</a>
<li><a href="cdt_u_prop_general_idx.htm">Indexer page</a>
<li><a href="cdt_u_prop_general_lng.htm">Language Mapping page</a>
<li>Paths and Symbols page
<ul>
<li><a href="cdt_u_prop_general_pns_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_pns_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_pns_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_pns_libpath.htm">Libraries path tab</a>
<li><a href="cdt_u_prop_general_pns_src.htm">Source Location tab</a>
<li><a href="cdt_u_prop_general_pns_out.htm">Output Location tab</a>
<li><a href="cdt_u_prop_general_pns_ref.htm">References tab</a>
<li><a href="cdt_u_prop_general_pns_hier.htm">Data Hierarchy tab</a>
</ul>
</ul>
<li><a href="cdt_u_prop_rundebug.htm">Run/Debug Settings page</a>
</ul>
</ul>
<li><a href="cdt_u_prop_ref.htm">C/C++ Project Properties, Project References page</a>
<li><a href="cdt_u_prop_rundebug.htm">C/C++ Project Properties, Run/Debug Settings page</a>
</ul>
</p>
<p><img src="../images/intl_07.gif" ALT="Intel Copyright Statement" ></p>

View file

@ -10,7 +10,7 @@
<body>
<h1>Language Mappings preferences</h1>
<h1>Language Mappings preferences</h1>
<p>Customize the use of C/C++ language associations in the <b>Language Mappings</b> preference panel for the workspace. </p>
<p><img src="../images/view_language_mappings_prefs.png" width="627" height="544"></p>

View file

@ -3,38 +3,45 @@
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>C/C++ Project Properties, Configurations management.</title>
<title>C/C++ Project Properties, Configuration management</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<h1>C/C++ Project Properties, Configurations management.</h1>
<h1>C/C++ Project Properties, Configuration management</h1>
All CDT-specific property pages have unified controls
to handle configurations.
<p><img img="" src="../images/prop_cfgs.png"
alt="C/C++ Project Properties, Configurations management."></p>
<p></p>
<dl>
<dt>Configuration:</dt>
<dd>Specifies the selected build configuration from the list provided.
Note that configuration selection, unlike CDT 3.x, affects only property pages contents.
Selected configuration would not be made Active configuration (used to build project).
</dd>
<dt>Manage configurations</dt>
<dd>Adds, removes, renames configurations. Sets active configuration. </dd>
</dl>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Configuration management properties</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td>Specifies the type of configuration(s) for the selected project. A <b>Debug</b> configuration lets you see what's going on "inside" a program as it executes. To debug your application, you must use executables compiled for debugging. These executables contain additional debug information that lets the debugger make direct associations between the source code and the binaries generated from the original source. A <b>Release</b> configuration provides the tools with options set to create an application with the best performance.</td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td>Opens the Manage Configurations dialog where you can set which configurations are active based on the toolchain(s) that were specified for the selected project. In addition, you can also create new configurations, rename an existing configuration, or remove ones that are no longer required.
<p><b>Note:</b>The <b>Configuration</b> selection that you specify in this dialog (unlike the behavior of CDT 3.x) affects only these property pages. This means that the selected configuration is not made the active configuration (the one used to build project).</p>
</td>
</tr>
</tbody>
</table>
<p><img border="0" src="../images/ngref.gif" alt="Related reference"
width="143" height="21"><br>
<ul>
<li><a href="cdt_u_prop_resource.htm">Project Properties, Resource page</a>
<li><a href="cdt_u_prop_builders.htm">Project Properties, Builders page</a>
<li><a href="cdt_u_prop_all.htm">Project Properties, common C/C++ Configurations handling</a>
<ul type="disc">
<li><a href="cdt_u_prop_manage_dialog.htm">Manage Configurations dialog</a>
<li><a href="cdt_u_prop_manage_newdialog.htm">Create Configuration dialog</a>
<li><a href="cdt_u_prop_manage_rendialog.htm">Rename Configuration dialog</a>
</ul>
<li><a href="cdt_u_prop_build.htm">Project Properties, C/C++ Build category</a>
<ul type="disc">
<li><a href="cdt_u_prop_build_discovery.htm">Discovery options page</a>
@ -53,13 +60,6 @@ Selected configuration would not be made Active configuration (used to build pro
<li>Project Properties, C/C++ General category
<ul type="disc">
<li><a href="cdt_u_prop_general_doc.htm">Documentation page</a>
<li><a href="cdt_u_prop_general_exp.htm">Export Settings page</a>
<!--ul>
<li><a href="cdt_u_prop_general_exp_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_exp_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_exp_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_exp_libpath.htm">Libraries path tab</a>
</ul-->
<li><a href="cdt_u_prop_general_typ.htm">File Types page</a>
<li><a href="cdt_u_prop_general_idx.htm">Indexer page</a>
<li><a href="cdt_u_prop_general_lng.htm">Language Mapping page</a>
@ -67,15 +67,13 @@ Selected configuration would not be made Active configuration (used to build pro
<ul>
<li><a href="cdt_u_prop_general_pns_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_pns_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_pns_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_pns_libpath.htm">Libraries path tab</a>
<li><a href="cdt_u_prop_general_pns_src.htm">Source Location tab</a>
<li><a href="cdt_u_prop_general_pns_out.htm">Output Location tab</a>
<li><a href="cdt_u_prop_general_pns_ref.htm">References tab</a>
<li><a href="cdt_u_prop_general_pns_hier.htm">Data Hierarchy tab</a>
</ul>
</ul>
<li><a href="cdt_u_prop_ref.htm">C/C++ Project Properties, Project References page</a>
<li><a href="cdt_u_prop_refactoring_history.htm">C/C++ Project Properties, Refactoring History page</a>
<li><a href="cdt_u_prop_rundebug.htm">C/C++ Project Properties, Run/Debug Settings page</a>
</ul>
</p>

View file

@ -10,74 +10,159 @@
<body>
<h1>C/C++ Project Properties, C/C++ Build</h1>
<p>This page serves as holder for all builder-specific property pages.
In addition, you can define settings for the Builder just on the place.<br>
Note that some settings ('Generate makefiles automatically', for example)
may affect other parameters (setting them disabled in some situations)
and, moreover, change visibility of other property pages.
<p>This page serves as the main window that contains all builder-specific property pages.
In addition, directly from this window you can define preferences for the <b>Builder settings</b> and <b>Behaviour</b> properties.
</p>
<p><b>Note:</b> Modifying some settings, such as the <b>Generate makefiles automatically</b> option, might affect other parameters (setting them from enabled to disabled in some situations)
and, moreover, change the visibility of other property pages.
</p>
<p><img img src="../images/prop_cbuild.png" alt="C/C++ Project Properties, C/C++ Build"></p>
<p><img img src="../images/prop_cbuild.png"
alt="C/C++ Project Properties, C/C++ Build"></p>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Builder settings preferences</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for its description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for its description.</a></td>
</tr>
<tr>
<td><dt>Builder type</dt></td>
<td>Specifies the type of builder to use: <b>Internal builder</b> (builds C/C++ programs using a compiler that implements the C/C++ Language Specificationt) and <b>External builder</b> (external tools let you configure and run programs and Ant buildfiles using the Workbench, which can saved and run at a later time to perform a build).</td>
</tr>
<tr>
<td><dt>Use default build command</dt></td>
<td>When enabled, this option indicates that you want to use the default <b>make</b> command. When disabled, it indicates the use of a new <b>make</b> command. This option is only available when the <b>Build type</b> option is set to <b>External</b>.</td>
</tr>
<tr>
<td><dt>Build command</dt></td>
<td>Specifies the default command used to start the build utility for your specific toolchain. Use this field if you want to use a build utility other than the default <b>make</b> command (when the <b>Use default build command</b> is not selected the field is active, and when you use an external builder or a custom makefile, you can provide your specific commands).</td>
</tr>
<tr>
<td><dt>Variables</dt></td>
<td>Opens the Select build variable dialog where you can add environment variables and custom variables to the build command.
<p><img img src="../images/prop_cbuild_selbldvar.png" alt="C/C++ Project Properties, C/C++ Build, Select build variable"></p>
<br>
</tr>
<tr>
<td><dt>Generate Makefiles automatically</dt></td>
<td>When selected, Eclipse changes between two different CDT modes: it either uses the customer's makefile for the build (referred to as a 'Standard Make project' in CDT 3.x) if one exists, or it generate makefiles for the user (called 'Managed build project' in CDT 3.x). By default, this option is automatically set.</td>
</tr>
<tr>
<td><dt>Expand Env. Variable Refs in Makefiles</dt></td>
<td>Defines whether environment variables ( ${xxx} ) should be expanded in makefile. By default, this option is automatically set.</td>
</tr>
<tr>
<td><dt>Build directory</dt></td>
<td>Defines the location where the build operation takes place. This location will contain the generated artifacts from the build process. This option is disabled when the <b>Generate Makefiles automatically</b> option is enabled.</td>
</tr>
<tr>
<td><dt>Workspace</dt></td>
<td>Opens the Folder Selection dialog where you can select a workspace location for the project. This is the directory that will contain the plug-ins and features to build, including any generated artifacts. This button is only visible when <b>Generate makefiles automatically</b> is set not selected.</td>
</tr>
<tr>
<td><dt>File system</dt></td>
<td>Opens the file system navigator where you can specify another file system to use. This button is only visible when <b>Generate makefiles automatically</b> is set not selected.</td>
</tr>
<tr>
<td><dt>Variables</dt></td>
<td>Opens the Select build variable dialog where you can select a variable to specify as an argument for, or create and configure simple build variables which you can reference in build configurations that support variables. This button is only visible when <b>Generate makefiles automatically</b> is set not selected.</td>
</tr>
</tbody>
</table>
<p><img img src="../images/prop_cbuild2.png" alt="C/C++ Project Properties, C/C++ Build"></p>
<dl>
<dt>Builder type</dt>
<dd>Select either internal or external builder</dd>
<dt>Use default build command</dt>
<dd>Select this checkbox to use the default make command.
Clear the check box to specify a new make command.
Available for external builder only.
</dd>
<dt>Build command</dt>
<dd>If you clear the <b>Use default</b> checkbox type a new make command in this field. Variables can be used.</dd>
<dt>Generate makefiles automatically</dt>
<dd>Switches between 2 CDT modes: either use customer's makefile for build (it was known as
'Standard Make project' in CDT 3.x), or generate makefiles ('Managed build project' in CDT 3.x).
</dd>
<dt>Expand env variable refs in Makefile</dt>
<dd>Defines whether environment variables ( ${xxx} ) should be expanded in makefile. Usually yes.</dd>
<dt>Stop on first build error</dt>
<dd>Stops building when any error occurs.</dd>
<dt>Use parallel build</dt>
<dd>Check this box if you want to use parallel project build</dd>
<dt>Use optimal jobs number</dt>
<dd>If parallel build enabled, lets builder to choose appropriate jobs number.</dd>
<dt>Use parallel jobs</dt>
<dd>If parallel build enabled, defines jobs number explicitly.</dd>
<dt>Workbench Build Behavior</dt>
<dd>These settings are what the builder will call by default when told to build, rebuild, clean, etc. You can change these so that new projects will use different targets if the defaults are not appropriate.</dd>
<dt>Build directory</dt>
<dd>Defines place where build operation is performed. Disabled when Makefiles Generation is ON.</dd>
</dl>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Behaviour preferences</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Stop on first build error</dt></td>
<td>Stops building when Eclipse encounters an error.
<p><b>Note:</b> If this option is not selected, it is helpful for building large projects because it tells <b>make</b> to continue making other independent rules even when one rule fails.</p></td>
</tr>
<tr>
<td><dt>Use parallel build</dt></td>
<td>When enabled, this option indicates the activation of the generation of parallel builds.
<p>If you enable this option, you need to determine the number of parallel jobs to perform:</p>
<ul>
<li><b>Use optimal jobs number</b> - Lets the system determine the optimal number of parallel jobs to perform.</li>
<li><b>Use parallel jobs</b> - Lets you specify the maximum number of parallel jobs to perform.</li>
</ul>
</td>
</tr>
<tr>
<td><dt>Workbench build behavior</dt></td>
<td>By default, the following settings are what the builder uses when instructed to build, rebuild, clean, and so on. You can change these settings so that new projects can use different targets if these defaults are not appropriate.</td>
</tr>
<tr>
<td><dt>Build on resource save (Auto build)</dt></td>
<td>When selected, builds your project whenever resources are saved. By default, this option is selected and builds occur automatically each time resources are modified. When this option is not selected, a build occurs only manually using a menu item. If you require more control over when builds occur (for example, when a build should wait until you finish a large assortment of changes), disable this option and manually invoke builds yourself.</td>
</tr>
<tr>
<td><dt>make build target</dt> ( for Build on resource save (Auto build))</td>
<td>To build your project when resources are saved and change the default <b>make</b> build target, enable the <b>Build on resource save (Auto Build)</b> option, and specify a new build target in the <b>Make build target</b> field.</td>
</tr>
<tr>
<td><dt>Variables</dt></td>
<td>Opens the Select build variable dialog where you can add variables to the build command.
<p><img img src="../images/prop_cbuild_selbldvar.png" alt="C/C++ Project Properties, C/C++ Build, Select build variable"></p>
</tr>
<tr>
<td><dt>Build (Incremental build)</dt></td>
<td>Defines what the builder calls when an incremental build is performed. When this option is enabled, an incremental build occurs meaning that only resources that have changed since the last build are considered. If this option is disabled, a full build occurs, meaning that all resources within the scope of the build are considered.
</td>
</tr>
<tr>
<td><dt>make build target</dt> (for Build (Incremental build))</td>
<td>To change the build default <b>make</b> build target, enable the <b>Build (Incremental build)</b> option, and specify a new build target in the <b>Make build target</b> field.</td>
</td>
</tr>
<tr>
<td><dt>Variables</dt></td>
<td>Opens the Select build variable dialog where you can add variables to the <b>make build target</b> command.</td>
</tr>
<tr>
<td><dt>Clean</dt></td>
<td>Defines what the builder calls when a clean is performed. The <b>make clean</b> is defined in the <b>makefile</b>.</td>
</tr>
<tr>
<td><dt>make build target</dt> (for Clean)</td>
<td>To change the rebuild default <b>make</b> build target, enable the <b>Clean</b> option, and specify a new build target in the <b>Make build target</b> field.</td>
</td>
</tr>
<tr>
<td><dt>Variables</dt></td>
<td>Opens the Select build variable dialog where you can add variables to the <b>make build target</b> command.</td></td>
</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>
<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 build settings</a></p>
<p><img border="0" src="../images/ngref.gif" ALT="Related reference" width="143" height="21"><br>
<p><img border="0" src="../images/ngref.gif" alt="Related reference"
width="143" height="21"><br>
<ul>
<li><a href="cdt_u_prop_resource.htm">Project Properties, Resource page</a>
<li><a href="cdt_u_prop_builders.htm">Project Properties, Builders page</a>
<li><a href="cdt_u_prop_all.htm">Project Properties, common C/C++ Configurations handling</a>
<ul type="disc">
<li><a href="cdt_u_prop_manage_dialog.htm">Manage Configurations dialog</a>
<li><a href="cdt_u_prop_manage_newdialog.htm">Create Configuration dialog</a>
<li><a href="cdt_u_prop_manage_rendialog.htm">Rename Configuration dialog</a>
</ul>
<li><a href="cdt_u_prop_build.htm">Project Properties, C/C++ Build category</a>
<ul type="disc">
<li><a href="cdt_u_prop_build_discovery.htm">Discovery options page</a>
@ -96,13 +181,6 @@ alt="C/C++ Project Properties, C/C++ Build"></p>
<li>Project Properties, C/C++ General category
<ul type="disc">
<li><a href="cdt_u_prop_general_doc.htm">Documentation page</a>
<li><a href="cdt_u_prop_general_exp.htm">Export Settings page</a>
<!--ul>
<li><a href="cdt_u_prop_general_exp_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_exp_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_exp_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_exp_libpath.htm">Libraries path tab</a>
</ul-->
<li><a href="cdt_u_prop_general_typ.htm">File Types page</a>
<li><a href="cdt_u_prop_general_idx.htm">Indexer page</a>
<li><a href="cdt_u_prop_general_lng.htm">Language Mapping page</a>
@ -110,18 +188,18 @@ alt="C/C++ Project Properties, C/C++ Build"></p>
<ul>
<li><a href="cdt_u_prop_general_pns_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_pns_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_pns_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_pns_libpath.htm">Libraries path tab</a>
<li><a href="cdt_u_prop_general_pns_src.htm">Source Location tab</a>
<li><a href="cdt_u_prop_general_pns_out.htm">Output Location tab</a>
<li><a href="cdt_u_prop_general_pns_ref.htm">References tab</a>
<li><a href="cdt_u_prop_general_pns_hier.htm">Data Hierarchy tab</a>
</ul>
</ul>
<li><a href="cdt_u_prop_ref.htm">C/C++ Project Properties, Project References page</a>
<li><a href="cdt_u_prop_refactoring_history.htm">C/C++ Project Properties, Refactoring History page</a>
<li><a href="cdt_u_prop_rundebug.htm">C/C++ Project Properties, Run/Debug Settings page</a>
</ul>
</p>
<p><img src="../images/intl_07.gif" ALT="Intel Copyright Statement" ></p>

View file

@ -7,50 +7,124 @@
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<h1>C/C++ Project Properties, Discovery Options</h1>
<p>You can define the discovery options on the Discovery Options page
of a C/C++ project's properties window.<br>
</p>
<dl>
</dl>
<p style="margin-left: 40px;"><img img=""
src="../images/prop_discovery.png"
alt="C/C++ Project Properties, Discovery Options"
><br>
</p>
<dl>
<dt>Discovery profile scope</dt>
<dd>Select either <b>per Language</b> or <b>Configuration-wide</b> scope.</dd>
<dt>Left pane (list)</dt>
<dd>When scope is 'per Language', select required language here.
In case of 'Configuration-wide' scope, only one item is displayed.</dd>
<h1>Discovery options preferences </h1>
<br>
<p style="margin-top: 0">Controls how to discover information required to build your project, enhance search and Content Assist functionality, and automatically enhance your makefile, such as include paths and symbol definitions.</p>
<p style="margin-top: 0">
<img border="0" src="../images/mpref_discovopts.png" </p>
<dt>Automate scanner configuration discovery</dt>
<dd>Select this checkbox to configure the automatic discovery of
paths and symbols. When unchecked, all controls below became disabled.</dd>
<dt>Report path detection problems</dt>
<dd>Enables or disables corresponding diagnostic messages.</dd>
<dt>Discovery profile</dt>
<dd>Select discovery profile from list.</dd>
<dt>Discovery profile options</dt>
<dd>This set of controls is profile-specific. It may vary from one profile to another.</dd>
</dl>
<p><img src="../images/ngref.gif" alt="Related reference" border="0"
height="21" width="143"><br>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Discovery options preferences</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Discovery Profiles Scope</dt></td>
<td>Specifies the type of profile to set for discovery:
<ul>
<li><b>Per Language</b> - Enables the association of different profiles with different resource types (different tools and input types), to have different settings discovered, e.g. for C and C++ source files and for different tools used by the project.
In addition, selecting this option lets you have different profile settings for different folders; however, only project profile types are allowed.
<li><b>Configuration-wide</b> - The Eclipse CDT uses only one profile for discovering scanner information for
the entire project (configuration). This means that both the project and per-file discovery profiles are allowed.
</ul>
</td>
</tr>
<tr>
<td>Left pane list (language specific)</td>
<td>Shows a list of language specific compilers. Select a language from the list.</td>
</tr>
<tr>
<td><dt>Automate discovery of paths and symbols</dt></td>
<td>Scans the build output to populate the path and symbol tables, such as symbol definitions, system include directories, local include directories, macros, and include files.</td>
</tr>
<tr>
<td><dt>Report path detection problems</dt></td>
<td>Sets the notification of diagnostic errors for include paths that the Eclipse CDT is unable to resolve as it parses the build output.</td>
</tr>
<tr>
<td><dt>Discovery profile</dt></td>
<td>Indicates the discovery profile to use for paths and symbol detection. The type of <b>Configuration</b> and <b>Discovery Profile Scope</b> you specify determine what which <b>Discovery Profile</b> options display on this tab.</td>
</tr>
<tr>
<td><dt>Enable build output scanner info discovery</dt></td>
<td>Configures the scanner to parse the output from a build for compiler commands with options that specify the definition of preprocessor symbols, and include search paths (for GCC compiler, -D and -I respectively). This button is only visible when <b>Configuration</b> is set to Release and the <b>Discovery Profiles Scope</b> is set to <b>Configuration-wide</b>.</td>
</tr>
<tr>
<td><dt>Load</dt></td>
<td>Lets you load a file to discover paths and symbols based on a previous builds' output. To activate the discovery select a build log file and then the <b>Load</b> button. This button is only visible when <b>Configuration</b> is set to Release and the <b>Discovery Profiles Scope</b> is set to <b>Configuration-wide</b>.
<p><b>Note:</b> Click <b>Variables</b> to open the Select Variables window to define a build output file.</p>
</td>
</tr>
<tr>
<td><dt>Load build output from file</dt></td>
<td>Specifies the name of the file you selected to load the build output from. This button is only visible when <b>Configuration</b> is set to Release and the <b>Discovery Profiles Scope</b> is set to <b>Configuration-wide</b>.</td>
</tr>
<tr>
<td><dt>Browse</dt></td>
<td>Click to locate a previously built output file to load the build output from. This button is only visible when <b>Configuration</b> is set to Release and the <b>Discovery Profiles Scope</b> is set to <b>Configuration-wide</b>.</td>
</tr>
<tr>
<td><dt>Variables</dt></td>
<td>Click to specify an argument for, or create and configure simple launch variables which you can reference in launch configurations that support variables. This button is only visible when <b>Configuration</b> is set to Release and the <b>Discovery Profiles Scope</b> is set to <b>Configuration-wide</b>.</td>
</tr>
<tr>
<td><dt>Enable generate scanner info command</dt></td>
<td>Enables the retrieval of information from the scanner. If it is not selected, the includes will be populated with default gcc system includes; Eclipse gathers the compiler settings based on the specified toolchain. This means that the Eclipse CDT can obtain the default gcc system includes to associate with the project.
<p>When selected, you can specify any required compiler specific commands in the <b>Compiler invocation command</b> field.</p>
</td>
</tr>
<tr>
<td><dt>Compiler invocation command</dt></td>
<td>Indicates the compiler specific command used to invoke the compiler (such as <tt>gcc</tt>, or more complicated commands used to perform all necessary steps for compiling C/C++ source files into .o files, and linking the object files and libraries into an executable program. For example, the command <b>gcc -E -P -v hello.c | hello.cpp</b> reads a compiler's configuration file and prints out information that includes the compiler's internally defined preprocessor symbols and include search paths. The information is complementary to the scanner configuration discovered when the output is parsed (if you've enabled the <b>Enable build output scanner info discovery</b> option), and is added to the project's scanner configuration. You can click <b>Browse</b> to locate this command, if required.
<p><b>Note:</b> The parsing of build output for scanner information is compiler specific. For example, the GNU toolchain compilers (gcc and g++) use -I for include paths, and -D for symbol definitions. Consult your compiler specific documentation for more information about scanner information commands, such as the following gcc commands:</p>
<ul>
<li><samp>-D <span style="font-style: italic;">name</span></samp></li>
<li><samp>-I</samp></li>
<li><samp>-U <span style="font-style: italic;">name</span></samp></li>
<li><samp>-I-</samp></li>
<li><samp>-nostdinc</samp></li>
<li><samp>-nostdinc++</samp></li>
<li><samp>-include <span style="font-style: italic;">file</span></samp></li>
<li><samp>-imacros <span style="font-style: italic;">file</span></samp></li>
<li><samp>-idirafter <span style="font-style: italic;">dir</span></samp></li>
<li><samp>-isystem <span style="font-style: italic;">dir</span></samp></li>
<li><samp>-iprefix <span style="font-style: italic;">prefix</span></samp></li>
<li><samp>-iwithprefix <span style="font-style: italic;">dir</span></samp></li>
<li><samp>-iwithprefixbefore <span style="font-style: italic;">dir</span></samp></li>
</ul>
</td>
</tr>
<tr>
<td><dt>Browse</dt></td>
<td>Click to browse for a file to include in the compiler invocation command. This button is only visible when <b>Configuration</b> is set to Release and the <b>Discovery Profiles Scope</b> is set to <b>Configuration-wide</b>.</td>
</tr>
</tbody>
</table>
<p><img border="0" src="../images/ngref.gif" alt="Related reference"
width="143" height="21"><br>
<ul>
<li><a href="cdt_o_mproj_pref_macro.htm">Build Project preferences, Macros</a>
<li><a href="cdt_u_prop_resource.htm">Project Properties, Resource page</a>
<li><a href="cdt_u_prop_builders.htm">Project Properties, Builders page</a>
<li><a href="cdt_u_prop_all.htm">Project Properties, common C/C++ Configurations handling</a>
<ul type="disc">
<li><a href="cdt_u_prop_manage_dialog.htm">Manage Configurations dialog</a>
<li><a href="cdt_u_prop_manage_newdialog.htm">Create Configuration dialog</a>
<li><a href="cdt_u_prop_manage_rendialog.htm">Rename Configuration dialog</a>
</ul>
<li><a href="cdt_u_prop_build.htm">Project Properties, C/C++ Build category</a>
<ul type="disc">
<li><a href="cdt_u_prop_build_discovery.htm">Discovery options page</a>
@ -69,13 +143,6 @@ paths and symbols. When unchecked, all controls below became disabled.</dd>
<li>Project Properties, C/C++ General category
<ul type="disc">
<li><a href="cdt_u_prop_general_doc.htm">Documentation page</a>
<li><a href="cdt_u_prop_general_exp.htm">Export Settings page</a>
<!--ul>
<li><a href="cdt_u_prop_general_exp_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_exp_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_exp_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_exp_libpath.htm">Libraries path tab</a>
</ul-->
<li><a href="cdt_u_prop_general_typ.htm">File Types page</a>
<li><a href="cdt_u_prop_general_idx.htm">Indexer page</a>
<li><a href="cdt_u_prop_general_lng.htm">Language Mapping page</a>
@ -83,19 +150,19 @@ paths and symbols. When unchecked, all controls below became disabled.</dd>
<ul>
<li><a href="cdt_u_prop_general_pns_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_pns_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_pns_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_pns_libpath.htm">Libraries path tab</a>
<li><a href="cdt_u_prop_general_pns_src.htm">Source Location tab</a>
<li><a href="cdt_u_prop_general_pns_out.htm">Output Location tab</a>
<li><a href="cdt_u_prop_general_pns_ref.htm">References tab</a>
<li><a href="cdt_u_prop_general_pns_hier.htm">Data Hierarchy tab</a>
</ul>
</ul>
<li><a href="cdt_u_prop_ref.htm">C/C++ Project Properties, Project References page</a>
<li><a href="cdt_u_prop_refactoring_history.htm">C/C++ Project Properties, Refactoring History
page</a>
<li><a href="cdt_u_prop_rundebug.htm">C/C++ Project Properties, Run/Debug Settings page</a>
</ul>
</p>
<p><img src="../images/intl_07.gif" ALT="Intel Copyright Statement" ></p>
<p><img src="../images/ng00_04a.gif" ALT="QNX Copyright Statement" ></p>
</body>
</html>

View file

@ -9,33 +9,77 @@
<body>
<h1>C/C++ Project Properties, Environment</h1>
Customizes the environment variables to be used in building selected configuration.
Customizes the build environment for all projects in the workspace; it lets you control the environment variables used by the build.
<p><img img="" src="../images/prop_environment.png"
alt="C/C++ Project Properties, Environment"></p>
<p></p>
<dl>
<dt>Environment variables to set</dt>
<dd>List of existing Eclipse-specific environment variables.
It is not the same as native environment variables list.
See details below.<br>
User-defined variables are marked with <b>bold font</b>.
</dd>
<dt>New...</dt>
<dd>Add new environment variable to the list</dd>
<dt>Select...</dt>
<dd>Add one or more native environment variable(s) to the list</dd>
<dt>Edit...</dt>
<dd>Change value of existing variable. If system variable is changed, it becames user's.</dd>
<dt>Remove</dt>
<dd>Removes selected variable. Note that some variables are read-only and cannot be removed.</dd>
<dt>Undefine</dt>
<dd>Clear variable's value but leave it present.</dd>
<dt>Append variables to native environment</dt>
<dd>Eclipse will be able to access both native environment and variables defined on this page.</dd>
<dt>Replace native environment with specified one</dt>
<dd>Eclipse will be able to access only variables defined on this page.</dd>
</dl>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Environment preference options</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Environment variables to set</dt></td>
<td>Shows the current list of environment variables and their corresponding value. These are the environment variable values used when building.</td>
</tr>
<tr>
<td><dt>Variable</dt></td>
<td>Specifies the name of the environment variable.</td>
</tr>
<tr>
<td><dt>Value</dt></td>
<td>Specifies the value of the environment variable.</td>
</tr>
<tr>
<td><dt>Append variables to native environment</dt></td>
<td>Appends the variables to the native environment during its execution.</td>
</tr>
<tr>
<td><dt>Replace native environment with specified one </dt></td>
<td>Replaces the native environment with the specified variables, and then restores the native environment upon its completion.</td>
</tr>
<tr>
<td><dt>New</dt></td>
<td>Opens a dialog to create a new environment variable and value. Custom environment variables that you create appear in bold within the list.
<p><img img="" src="../images/cdt_buildenv_newenvvar.png" alt="C/C++ Project Properties, Environment, New environment variable"></p> <br>
<p>Click <b>Variables</b> to Select variables by name to include in the value. Select <b>Add to all configurations</b> to make this new environment variable available to all configurations for the selected project; otherwise, the variable is only available for the currently selected configuration.</p>
</td>
</tr>
<tr>
<td><dt>Select</dt></td>
<td>Opens the Select variables dialog where you can choose from a list of system variables.
<p><img img="" src="../images/cdt_buildenv_selectvar.png" alt="C/C++ Project Properties, Environment, New environment variable"></p></td>
</td>
</tr>
<tr>
<td><dt>Edit</dt></td>
<td>Modifies the name and value of the selected environment variable.</td>
</tr>
<tr>
<td><dt>Remove</dt></td>
<td>Removes the selected environment variables from the list.</td>
</tr>
<tr>
<td><dt>Undefine</dt></td>
<td>Undefines the currently selected variable; however, some variables, such as the PATH variable, cannot be undefined.
</td>
</tr>
</tbody>
</table>
<p style="margin-top: 0pt; margin-bottom: 0pt;"><img border="0"
src="../images/ngref.gif" alt="Related reference" width="143"
height="21"><br>

View file

@ -8,24 +8,53 @@
</head>
<body>
<h1>C/C++ Properties, Build, Settings, Build Artifact tab</h1>
<p>Lets you specify build artifact information, such as the type and name, that gets built by the selected build configuration.</p>
<p><img img="" src="../images/prop_artifact.png"
alt="C/C++ Properties, Build, Settings, Build Artifact tab"></p>
<p></p>
<dl>
<dt>Artifact Type:</dt>
<dd>Select artifact type that is built by the selected build
configuration (executable, static library, shared library).</dd>
<dt>Artifact name:</dt>
<dd>Specify name of artifact. By default, the same as project name</dd>
<dt>Artifact extension:</dt>
<dd>Specify artifact extension.</dd>
<dt><br>Available for :</dt>
<dd>CDT projects</dd>
</dl>
<p><img border="0" src="../images/ngref.gif" alt="Related reference"
width="143" height="21"><br>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Build artifact options</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Artifact Type</dt></td>
<td>Show the type for the selected artifact. Select an artifact type that is built by the currently selected build configuration (such as an <b>Executable</b>, </b>Static library</b>, and <b>Shared library</b>).</td>
</tr>
<tr>
<td><dt>Artifact name</dt></td>
<td>Indicates the name of artifact. By default, the name is the same as project name.</td>
</tr>
<tr>
<td><dt>Artifact extension</dt></td>
<td>Specifies the file extension for the specified artifact type.</td>
</tr>
<tr>
<td><dt>Output prefix</dt></td>
<td>Indicates a prefix that you want to prepend to the output results. </td>
</tr>
</tbody>
</table>
<br>
<p><b>Available for:</b> CDT projects.</p>
<p style="margin-top: 0pt; margin-bottom: 0pt;"><img border="0"
src="../images/ngref.gif" alt="Related reference" width="143"
height="21"><br>
<ul>
<li><a href="cdt_u_prop_resource.htm">Project Properties, Resource page</a>

View file

@ -9,36 +9,63 @@
<body>
<h1>C/C++ Project Properties, Build, Settings, Binary Parser</h1>
<p>You can select the Binary Parsers you require for a project to
ensure the accuracy of the C/C++ Projects view and to successfully run
ensure the accuracy of the C/C++ Projects view, and to successfully run
and debug your programs. After you select the correct parser for your
development environment and build your project, you can view the
symbols of the object file in the C/C++ Projects view.</p>
symbols of the object file using the C/C++ Projects view.</p>
<p><img img="" src="../images/prop_bin.png"
alt="C/C++ Project Properties, Build, Settings, Binary Parser"></p>
<dl>
<dt>Binary Parser (left pane)</dt>
<dd>List of all binary parsers known to CDT.<br>
Mark parsers you wish to use with checkmark.<br>
Select corresponding line to edit parser's options, if any</dd>
<dt>'Move up' and 'Move down' </dt>
<dd>Move selected parser upper (or lower) in list. Note that order matters
for checked parsers only: they are applied to binaries in the
same sequence as defined by user. Order is not preserved for unchecked
parsers, so it's useless to move them up/down.
</dd>
<dt>Binary Parser Option</dt>
<dd>Parser-specific parameters. Different parsers may have different options list (in particular, they may have no options at all).</dd>
<dt><br>Available for :</dt>
<dd>CDT projects</dd>
</dl>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Binary parser options</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Binary Parser</dt> (top pane)</td>
<td>Lists all of the binary parsers currently known to CDT. Select the parsers that you want to use, and select the corresponding line to edit parser's options, if required.</td>
</tr>
<tr>
<td><dt>Binary Parser Option</dt></td>
<td>Shows the parameters for the currently selected parser in the list above. Depending on the parser you select, the options in the list will be different (in particular, some may have no options at all).</td>
</tr>
<tr>
<td><dt>Move up</dt></td>
<td>Moves the selected parser higher in list. <b>Note:</b> The order matters for selected parsers only: they are applied to binaries in the same sequence as defined by the user. The order is not preserved for unchecked parsers, so you do not have to move them.</td>
</tr>
<tr>
<td><dt>Move down</dt></td>
<td>Move the selected parser lower in list. <b>Note:</b> The order matters for selected parsers only: they are applied to binaries in the same sequence as defined by the user. The order is not preserved for unchecked parsers, so you do not have to move them.</td>
</tr>
</tbody>
</table>
<br>
<p><b>Available for:</b> CDT projects.</p>
<p><img border="0" src="../images/ngtasks.gif" alt="Related tasks"
width="143" height="21">
<br>
<a href="../tasks/cdt_t_proj_parser.htm">Selecting a binary parser</a></p>
<p><img border="0" src="../images/ngref.gif" alt="Related reference"
width="143" height="21"><br>
<p style="margin-top: 0pt; margin-bottom: 0pt;"><img border="0"
src="../images/ngref.gif" alt="Related reference" width="143"
height="21"><br>
<ul>
<li><a href="cdt_u_prop_resource.htm">Project Properties, Resource page</a>

View file

@ -8,35 +8,62 @@
</head>
<body>
<h1>C/C++ Project Properties, Build, Settings, Error Parsers</h1>
<p>Customizes the list of the filters that detect error patterns in the
<p>Customizes the list of filters that detect error patterns in the
build output log.</p>
<p><img img="" src="../images/prop_error.png"
alt="C/C++ Project Properties, Build, Settings, Error Parsers"></p>
<dl>
<dt>Error Parsers (left pane)</dt>
<dd>List of all error parsers known to CDT.<br>
Mark parsers you wish to use with checkmark.<br>
Select corresponding line to edit parser's options, if any</dd>
<dt>'Move up' and 'Move down' </dt>
<dd>Move selected parser upper (or lower) in list. Note that order matters
for checked parsers only: they are applied to error logs in the
same sequence as defined by user. Order is not preserved for unchecked
parsers, so it's useless to move them up/down.
<dt>Check all</dt>
<dd>Makes all error parsers selected.</dd>
<dt>Uncheck all</dt>
<dd>Makes all error parsers unselected.</dd>
<dt><br>Available for :</dt>
<dd>CDT projects</dd>
</dl>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Binary parser options</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Error Parsers</dt></td>
<td>Lists all of the error parsers currently known to CDT. Select the parsers that you want to use, and select the corresponding line to edit parser's options, if required.</td>
</tr>
<tr>
<td><dt>Move up</dt></td>
<td>Moves the selected parser higher in list. <b>Note:</b> The order matters for selected parsers only: they are applied to error logs in the same sequence as defined by the user. The order is not preserved for unchecked parsers, so you do not have to move them.</td>
</tr>
<tr>
<td><dt>Move down</dt></td>
<td>Move the selected parser lower in list. <b>Note:</b> The order matters for selected parsers only: they are applied to error logs in the same sequence as defined by the user. The order is not preserved for unchecked parsers, so you do not have to move them.</td>
</tr>
<tr>
<td><dt>Check all</dt></td>
<td>Selects all error parsers in the list.</td>
</tr>
<tr>
<td><dt>Uncheck all</dt></td>
<td>Makes all error parsers in the list unselected.</td>
</tr>
</tbody>
</table>
<br>
<p><b>Available for:</b> CDT projects.</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">Filtering errors</a></p>
<p><img border="0" src="../images/ngref.gif" alt="Related reference"
width="143" height="21"><br>
<p style="margin-top: 0pt; margin-bottom: 0pt;"><img border="0"
src="../images/ngref.gif" alt="Related reference" width="143"
height="21"><br>
<ul>
<li><a href="cdt_u_prop_resource.htm">Project Properties, Resource page</a>

View file

@ -8,57 +8,78 @@
</head>
<body>
<h1>C/C++ Properties, Build, Settings, Build Steps tab</h1>
Customizes the selected build configuration allowing the specification
of user defined build command steps, as well as a descriptive message
to be displayed in the
build output, immediately prior to and immediately after normal build
processing executes.
<p>Customizes the selected build configuration allowing for the specification
of user defined build command steps, as well displaying a descriptive message
in the build output, immediately before and after, normal build
processing executes.</p>
<p><img img="" src="../images/prop_steps.png"
alt="C/C++ Properties, Build, Settings, Build Steps tab"></p>
<p></p>
<dl>
<dt>Pre-build Steps</dt>
<dt>&nbsp;&nbsp;&nbsp; Command</dt>
<dd>Specifies a command, or a list of semicolon separated commands,
to be executed immediately prior to execution of the build.</dd>
<dt>&nbsp;&nbsp;&nbsp; Description</dt>
<dd>Specifies optional descriptive text that is associated with the
pre-build step to be displayed in the build output immediately prior to
execution of the pre-build step command or commands.</dd>
<dt>Post-build Steps</dt>
<dt>&nbsp;&nbsp;&nbsp; Command</dt>
<dd>Specifies a command, or a list of semicolon separated commands,
to be executed immediately after the execution of the build.</dd>
<dt>&nbsp;&nbsp;&nbsp; Description</dt>
<dd>Specifies optional descriptive text that is associated with the
post-build step to be displayed in the build output immediately prior
to execution of the post-build step command or commands.</dd>
<dt><br>Available for :</dt>
<dd>CDT projects</dd>
</dl>
<h2></h2>
<h2>Detailed Specification</h2>
<p>To ensure reasonable custom build step behavior, sensible input must
be provided when specifying custom build step input. Custom build steps
<p><b>Note:</b> To ensure reasonable custom build step behavior, sensible input must
be provided when specifying custom build step information. Custom build steps
are not verified for correctness in any regard and are passed exactly
as entered into the build stream. <br>
<br>
In the descriptive text, below, the term "main build" is defined as the
sequence of commands to be executed when a build is invoked, not
sequence of commands to execute when a build is invoked, not
including pre-build or post-build steps.<br>
<br>
The pre-build step is not executed if the state of the main build is
determined to be up to date; otherwise it is executed. An attempt to
execute the main build will occur regardless of the success or failure
of executing the pre-build step.
<br>
<br>
The post-build step is not executed if the state of the main build is
determined to be up to date. It will be executed only if the main-build
has executed successfully. </p>
</p>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Build step options</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Pre-build Steps</dt></td>
<td>Identifies any steps that are to occur before the build takes place.
<p><b>Note:</b> The pre-build step is not executed if the state of the main build is determined to be up to date; otherwise it is executed. An attempt to execute the main build will occur regardless of the success or failure of executing the pre-build step.</p>
</td>
</tr>
<tr>
<td><dt>Command</dt></td>
<td>Specifies one or more commands to execute immediately before the execution of the build. Use semicolons to separate multiple commands.</td>
</tr>
<tr>
<td><dt>Description</dt></td>
<td>Specifies optional descriptive text associated with the pre-build step that is displayed in the build output immediately before the execution of the pre-build step command (or commands).</td>
</tr>
<tr>
<td><dt>Post-build steps</dt></td>
<td>Identifies any steps that are to occur after the build takes place.
<p><b>Note:</b> The post-build step is not executed if the state of the main build is determined to be up to date. It will be executed only if the main-build has executed successfully.</p>
</td>
</tr>
<tr>
<td><dt>Command</dt></td>
<td>Specifies one or more commands to execute immediately after the execution of the build. Use semicolons to separate multiple commands.</td>
</tr>
<tr>
<td><dt>Description</dt></td>
<td>Specifies optional descriptive text associated with the post-build step that is displayed in the build output immediately after the execution of the post-build step command (or commands).</td>
</tr>
</tbody>
</table>
<br>
<p><b>Available for:</b> CDT projects.</p>
<p style="margin-top: 0pt; margin-bottom: 0pt;"><img border="0"
src="../images/ngref.gif" alt="Related reference" width="143"
height="21"><br>
<p><img border="0" src="../images/ngref.gif" alt="Related reference"
width="143" height="21"><br>
<ul>
<li><a href="cdt_u_prop_resource.htm">Project Properties, Resource page</a>

View file

@ -3,26 +3,49 @@
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>C/C++ Project Properties, Build, Settings, Tool Settings tab </title>
<title>C/C++ Project Properties, Build, Settings, Tool settings tab </title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<h1>C/C++ Project Properties, Build, Settings, Tool Settings tab</h1>
<h1>C/C++ Project Properties, Build, Settings, Tool settings tab</h1>
Customizes the tools and tool options used in your build configuration.
<p><img img="" src="../images/prop_tool.png"
alt="C/C++ Project Properties, Build, Settings, Tool Settings tab"></p>
<p></p>
<dl>
<dt>Left pane:</dt>
<dd>Displays list of tools and their option categories. Select required line to edit its options.</dd>
<dt>Right pane:</dt>
<dd>List of options for selected tool or category.
</dd>
<dt><br>Available for :</dt>
<dd>CDT projects and source files</dd>
</dl>
<p><img border="0" src="../images/ngref.gif" alt="Related reference"
width="143" height="21"><br>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Tool settings options</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td>(Left pane)</td>
<td>Displays a list of tools and their option categories. Select a desired tool from the list to modify its options.</tr>
<tr>
<td>(Right pane)</td>
<td>Displays the options that you can modify for the selected tool. This list of options changes depending on which options category you select for a specific tool in the left pane.</td>
</tr>
</tbody>
</table>
<br>
<p><b>Available for:</b> CDT projects and source files</p>
<p style="margin-top: 0pt; margin-bottom: 0pt;"><img border="0"
src="../images/ngref.gif" alt="Related reference" width="143"
height="21"><br>
<ul>
<li><a href="cdt_u_prop_resource.htm">Project Properties, Resource page</a>

View file

@ -7,37 +7,59 @@
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<h1>C/C++ Project Properties, Tool Chain edit</h1>
Customizes the toolchain used in your build configuration.
<p><img img="" src="../images/prop_tc_edit.png"
alt="C/C++ Project Properties, Tool Chain edit"></p>
<p></p>
<dl>
<dt>Display compatible toolchains only.</dt>
<dd>Allows to show either all toolchains known to CDT, or compatible ones only.
Toolchain is compatible if it can run on given platform.</dd>
<dt>Current toolchain</dt>
<dd>Select the toolchain to be used with selected configuration.</dd>
<dt>Current builder</dt>
<dd>Select builder to be used to build selected configuration.</dd>
<dt>Used tools</dt>
<dd>A list of tools currently included to selected toolchain.
User can modify it (add/remove tools) by 'Select tools' button.</dd>
<dt><br>Available for :</dt>
<dd>CDT projects only</dd>
</dl>
<h1>Tool chain editor preferences (C/C++ Project Properties)</h1>
<br>
<p style="margin-top: 0">Customizes the toolchain used in your build configuration; it lets
you specify which tools the builder needs to include when it builds the project for a specified toolchain and configuration.</p>
<p style="margin-top: 0">
<img border="0" src="../images/mpref_toolchain.png" </p>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Tool chain editor properties</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Configuration</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Display compatible toolchains only</dt></td>
<td>When selected, it shows a list of toochains that are only compatible with the current configuration. When this option is not selected, it shows a list of all toolchains known to the Eclipse CDT. A Toolchain is compatible if it can run on given platform. .</td>
</tr>
<tr>
<td><dt>Current toolchain</dt></td>
<td>Indicates the toolchain to use with the current configuration. A toolchain is a set of tools (such as a compiler, linker, and assembler) intended to build your project. Additional tools, such as a debugger, can be associated with a toolchain. There can be several toolchains available, depending on the compilers installed on your system.</td>
</tr>
<tr>
<td><dt>Current builder</dt></td>
<td>Indicates the builder used to build the selected configuration. A builder refers to an external <b>make</b> utility, such as GNU make, that the Eclipse CDT uses (and relies on) to build a project. The CDT can generate <b>makefiles</b> automatically when you create a Make C or C++ project, or you have the option of creating a C or C++ Make project where you provide the makefile yourself.</td>
</tr>
<tr>
<td><dt>Used tools</dt></td>
<td>Shows a list of tools currently included for the selected toolchain. You can click <b>Select Tools</b> to modify this list.</td>
</tr>
<tr>
<td><dt>Select Tools</dt></td>
<td>Opens the Select Tools dialog that lets you add or remove tools from the list of tools for the selected toolchain.</td>
</tr>
</tbody>
</table>
<br>
<p><img border="0" src="../images/ngref.gif" alt="Related reference"
width="143" height="21"><br>
<ul>
<li><a href="cdt_u_prop_resource.htm">Project Properties, Resource page</a>
<li><a href="cdt_u_prop_builders.htm">Project Properties, Builders page</a>
<li><a href="cdt_u_prop_all.htm">Project Properties, common C/C++ Configurations handling</a>
<ul type="disc">
<li><a href="cdt_u_prop_manage_dialog.htm">Manage Configurations dialog</a>
<li><a href="cdt_u_prop_manage_newdialog.htm">Create Configuration dialog</a>
<li><a href="cdt_u_prop_manage_rendialog.htm">Rename Configuration dialog</a>
</ul>
<li><a href="cdt_u_prop_build.htm">Project Properties, C/C++ Build category</a>
<ul type="disc">
<li><a href="cdt_u_prop_build_discovery.htm">Discovery options page</a>
@ -56,13 +78,6 @@ Customizes the toolchain used in your build configuration.
<li>Project Properties, C/C++ General category
<ul type="disc">
<li><a href="cdt_u_prop_general_doc.htm">Documentation page</a>
<li><a href="cdt_u_prop_general_exp.htm">Export Settings page</a>
<!--ul>
<li><a href="cdt_u_prop_general_exp_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_exp_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_exp_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_exp_libpath.htm">Libraries path tab</a>
</ul-->
<li><a href="cdt_u_prop_general_typ.htm">File Types page</a>
<li><a href="cdt_u_prop_general_idx.htm">Indexer page</a>
<li><a href="cdt_u_prop_general_lng.htm">Language Mapping page</a>
@ -70,15 +85,15 @@ Customizes the toolchain used in your build configuration.
<ul>
<li><a href="cdt_u_prop_general_pns_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_pns_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_pns_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_pns_libpath.htm">Libraries path tab</a>
<li><a href="cdt_u_prop_general_pns_src.htm">Source Location tab</a>
<li><a href="cdt_u_prop_general_pns_out.htm">Output Location tab</a>
<li><a href="cdt_u_prop_general_pns_ref.htm">References tab</a>
<li><a href="cdt_u_prop_general_pns_hier.htm">Data Hierarchy tab</a>
</ul>
</ul>
<li><a href="cdt_u_prop_ref.htm">C/C++ Project Properties, Project References page</a>
<li><a href="cdt_u_prop_refactoring_history.htm">C/C++ Project Properties, Refactoring History
page</a>
<li><a href="cdt_u_prop_rundebug.htm">C/C++ Project Properties, Run/Debug Settings page</a>
</ul>
</p>

View file

@ -3,44 +3,79 @@
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>C/C++ Project Properties, Variables</title>
<title>Variables properties (C/C++ Project Properties)</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<h1>C/C++ Project Properties, Variables</h1>
Customizes CDT build variables (known as Build macros in CDT 3.x) to be used in building selected configuration.
<h1>Variables properties (C/C++ Project Properties)</h1>
Customizes the Eclipse CDT build environment variables for all projects in the workspace; it lets
you control the environment variables used by the build to for the purposes of building the selected configuration.</p>
<p><img img="" src="../images/prop_variables.png"
alt="C/C++ Project Properties, Variables"></p>
<p></p>
<dl>
<dt>Table in the center</dt>
<dd>List of CDT Build variables. They can be defined either by user or by CDT. User's variables will be marked with <b>bold</b> font.</dd>
<dt>Add</dt>
<dd>Define new user's CDT Build variable</dd>
<dt>Edit</dt>
<dd>Change CDT Build variable. If system variable is changed, it's saved as user's and 'screens' original one.</dd>
<dt>Delete</dt>
<dd>Removes user's CDT Build variable</dd>
<dt>Show system variable</dt>
<dd>Defines whether Build variables defined by CDT should be shown.</dd>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Variables preferences</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Environment variables to set</dt></td>
<td>Shows the current list of environment variables and their corresponding value. These are the environment variable values used when running an application.</td>
</tr>
<tr>
<td><dt>Configuration</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>Manage configurations</dt></td>
<td><a href="cdt_u_prop_all.htm">Click here for a description.</a></td>
</tr>
<tr>
<td><dt>(The variables table)</dt></td>
<td>Lists the CDT build variables and system variables, by <b>Name</b>, <b>Type</b>, and the <b>Value</b>. Custom Build variables are identified by the name being highlighted using a <b>bold</b> font.</td>
</tr>
<tr>
<td><dt>Name</dt></td>
<td>Indicates the name of the variable, either a user defined variable or a system variable.</td>
</tr>
<tr>
<td><dt>Type</dt></td>
<td>Shows the type for the variable.</td>
</tr>
<tr>
<td><dt>Value</dt></td>
<td>Specifies the value of the variable.</td>
</tr>
<tr>
<td><dt>Show system variables</dt></td>
<td>When selected, system variables are included in the Variables table; otherwise, they are excluded so that only user defined variables appear in the Variables list.</td>
</tr>
<tr>
<td><dt>Add</dt></td>
<td>Creates a new variable and corresponding value.</td>
</td>
</tr>
<tr>
<td><dt>Edit</dt></td>
<td>Modifies the name and value of the selected variable.</tr>
<tr>
<td><dt>Delete</dt></td>
<td>Removes the selected variables from the list. <b>Note:</b> Some variables are read-only and cannot be removed.
</td>
</tr>
</tbody>
</table>
<!--dt><br>Available for :</dt>
<dd>Any projects, folders and files regardless of project kind</dd-->
</dl>
<p style="margin-top: 0pt; margin-bottom: 0pt;"><img border="0"
src="../images/ngref.gif" alt="Related reference" width="143"
height="21"><br>
<p><img border="0" src="../images/ngref.gif" alt="Related reference"
width="143" height="21"><br>
<ul>
<li><a href="cdt_u_prop_resource.htm">Project Properties, Resource page</a>
<li><a href="cdt_u_prop_builders.htm">Project Properties, Builders page</a>
<li><a href="cdt_u_prop_all.htm">Project Properties, common C/C++ Configurations handling</a>
<ul type="disc">
<li><a href="cdt_u_prop_manage_dialog.htm">Manage Configurations dialog</a>
<li><a href="cdt_u_prop_manage_newdialog.htm">Create Configuration dialog</a>
<li><a href="cdt_u_prop_manage_rendialog.htm">Rename Configuration dialog</a>
</ul>
<li><a href="cdt_u_prop_build.htm">Project Properties, C/C++ Build category</a>
<ul type="disc">
<li><a href="cdt_u_prop_build_discovery.htm">Discovery options page</a>
@ -59,13 +94,6 @@ Customizes CDT build variables (known as Build macros in CDT 3.x) to be used in
<li>Project Properties, C/C++ General category
<ul type="disc">
<li><a href="cdt_u_prop_general_doc.htm">Documentation page</a>
<li><a href="cdt_u_prop_general_exp.htm">Export Settings page</a>
<!--ul>
<li><a href="cdt_u_prop_general_exp_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_exp_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_exp_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_exp_libpath.htm">Libraries path tab</a>
</ul-->
<li><a href="cdt_u_prop_general_typ.htm">File Types page</a>
<li><a href="cdt_u_prop_general_idx.htm">Indexer page</a>
<li><a href="cdt_u_prop_general_lng.htm">Language Mapping page</a>
@ -73,18 +101,19 @@ Customizes CDT build variables (known as Build macros in CDT 3.x) to be used in
<ul>
<li><a href="cdt_u_prop_general_pns_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_pns_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_pns_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_pns_libpath.htm">Libraries path tab</a>
<li><a href="cdt_u_prop_general_pns_src.htm">Source Location tab</a>
<li><a href="cdt_u_prop_general_pns_out.htm">Output Location tab</a>
<li><a href="cdt_u_prop_general_pns_ref.htm">References tab</a>
<li><a href="cdt_u_prop_general_pns_hier.htm">Data Hierarchy tab</a>
</ul>
</ul>
<li><a href="cdt_u_prop_ref.htm">C/C++ Project Properties, Project References page</a>
<li><a href="cdt_u_prop_refactoring_history.htm">C/C++ Project Properties, Refactoring History
page</a>
<li><a href="cdt_u_prop_rundebug.htm">C/C++ Project Properties, Run/Debug Settings page</a>
</ul>
</p>
<p><img src="../images/intl_07.gif" ALT="Intel Copyright Statement" ></p>
</body>

View file

@ -13,36 +13,66 @@ which order they are used.</p>
<p><img img="" src="../images/prop_builders.png"
alt="C/C++ Project Properties, Builders"></p>
<p></p>
<dl>
<dt>Configure the builders for the project</dt>
<dd>Selects which Builders to enable.</dd>
<dt>New...</dt>
<dd>Adds a new builder.</dd>
<dt>Import...</dt>
<dd>Imports a builder.</dd>
<dt>Edit...</dt>
<dd>Edits a builder.</dd>
<dt>Remove</dt>
<dd>Removes a builder.</dd>
<dt>Up</dt>
<dd>Moves the currently selected builder higher in the list.</dd>
<dt>Down</dt>
<dd>Moves the currently selected builder lower in the list.</dd>
<dt><br>Available for :</dt>
<dd>Any projects, folders and files regardless of project kind</dd>
</dl>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Builder properties</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Configure the builders for the project</dt></td>
<td>Selects which builders to enable from the list. You can disable the CDT Builder and you can control when the CDT Builder runs with respect to the project builders that you define.
</td>
</tr>
<tr>
<td><dt>New...</dt></td>
<td>Opens the Choose configuration type dialog so that you can add a new builder to the list. <p>
</p><p><img img="" src="../images/prop_builders_newbldr.png"
alt="C/C++ Project Properties, Builders, Choose configuration type"></p>
<p>The <b>Ant Builder</b> option lets you configure and deploy projects; however, if you want to use some other tool or prefer to do it yourself, you can set up a <b>Program</b> external tool project builder. This type allows you to customize the deployment of your project as you require, while maintaining the convenience of automatically running your script every time your project is built.</p>
<p>The <b>Program</b> option lets you to define an external tool for any executable file that is accessible on your local or network file system. For example, if instead of Ant you prefer to use your own shell scripts or Windows .bat files to package and deploy your Eclipse projects, you can then create a <b>Program</b> external tool that would specify where and how to execute that script.</p></tr>
<tr>
<td><dt>Import...</dt></td>
<td>Opens the Import launch configuration dialog so that you can import a builder to include it in the list.<p></p>
</p><p><img img="" src="../images/prop_builders_imprtlnchcnfg.png"
<p></p></tr>
<tr>
<td><dt>Edit...</dt></td>
<td>Opens the Configure Builder dialog that lets you specify when to run the selected builder.<p></p>
</p><p><img img="" src="../images/prop_builders_editbldr.png"
<p></p>
<p>When you configure a builder, you have the following options:
<ul>
<li><b>After a "Clean"</b> - When enabled, the selected builder is scheduled to run after a <b>clean</b> operation occurs.
<li><b>During manual builds</b> - When enabled, the selected build is initiated when you explicitly select a menu item or press its corresponding shortcut key combination.
<li><b>During auto builds</b> - When enabled, automatic builds are performed as resources are saved (they are incremental and operate over an entire workspace). <b>Note:</b> running your project builder during auto builds is possible, although it is not recommended because of performance concerns.
<li><b>During a "Clean"</b> - When enabled, the selected builder is scheduled to run during a <b>clean</b> operation.
</p></tr>
<tr>
<td><dt>Remove</dt></td>
<td>Removes the selected builder from the list.</tr>
<tr>
<td><dt>Up</dt></td>
<td>Moves the currently selected builder higher in the list to change the builder order.</tr>
<tr>
<td><dt>Down</dt></td>
<td>Moves the currently selected builder lower in the list to change the builder order.</tr>
</tbody>
</table>
<br>
<p><b>Available for:</b> Any projects, folders and files regardless of project kind.</p>
<p><img border="0" src="../images/ngref.gif" alt="Related reference"
width="143" height="21"><br>
<ul>
<li><a href="cdt_u_prop_resource.htm">Project Properties, Resource page</a>
<li><a href="cdt_u_prop_builders.htm">Project Properties, Builders page</a>
<li><a href="cdt_u_prop_all.htm">Project Properties, common C/C++ Configurations handling</a>
<ul type="disc">
<li><a href="cdt_u_prop_manage_dialog.htm">Manage Configurations dialog</a>
<li><a href="cdt_u_prop_manage_newdialog.htm">Create Configuration dialog</a>
<li><a href="cdt_u_prop_manage_rendialog.htm">Rename Configuration dialog</a>
</ul>
<li><a href="cdt_u_prop_build.htm">Project Properties, C/C++ Build category</a>
<ul type="disc">
<li><a href="cdt_u_prop_build_discovery.htm">Discovery options page</a>
@ -61,13 +91,6 @@ which order they are used.</p>
<li>Project Properties, C/C++ General category
<ul type="disc">
<li><a href="cdt_u_prop_general_doc.htm">Documentation page</a>
<li><a href="cdt_u_prop_general_exp.htm">Export Settings page</a>
<!--ul>
<li><a href="cdt_u_prop_general_exp_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_exp_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_exp_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_exp_libpath.htm">Libraries path tab</a>
</ul-->
<li><a href="cdt_u_prop_general_typ.htm">File Types page</a>
<li><a href="cdt_u_prop_general_idx.htm">Indexer page</a>
<li><a href="cdt_u_prop_general_lng.htm">Language Mapping page</a>
@ -75,15 +98,15 @@ which order they are used.</p>
<ul>
<li><a href="cdt_u_prop_general_pns_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_pns_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_pns_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_pns_libpath.htm">Libraries path tab</a>
<li><a href="cdt_u_prop_general_pns_src.htm">Source Location tab</a>
<li><a href="cdt_u_prop_general_pns_out.htm">Output Location tab</a>
<li><a href="cdt_u_prop_general_pns_ref.htm">References tab</a>
<li><a href="cdt_u_prop_general_pns_hier.htm">Data Hierarchy tab</a>
</ul>
</ul>
<li><a href="cdt_u_prop_ref.htm">C/C++ Project Properties, Project References page</a>
<li><a href="cdt_u_prop_refactoring_history.htm">C/C++ Project Properties, Refactoring History
page</a>
<li><a href="cdt_u_prop_rundebug.htm">C/C++ Project Properties, Run/Debug Settings page</a>
</ul>
</p>

View file

@ -7,13 +7,21 @@
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<h1>C/C++ Project Properties, Managed, Refactoring History</h1>
<h1>C/C++ Project Properties, Refactoring History</h1>
<p>Lets you explore the entire refactoring history for the currently selected project.</p>
<p><img img="" src="../images/mprop_refactoring_history.png"
alt="C/C++ Project, Managed, Refactoring History "></p>
<p></p>
<dl>
<dt>Refactoring history for &lt;project&gt;:</dt>
<dd>Allows exploring of refactorings done on this project.</dd>
<dd>The refactoring history dialog displays the entire refactoring history of your workspace. Drill down to an individual refactoring and select it to see more details about the performed refactoring in the details view below.
This dialog may also be used to remove certain refactorings from the refactoring history. Select an entire year, month, week or day and press Remove to remove the selected refactorings from the refactoring history.
In order to be able to better select refactorings from the refactoring history, there are two ways to group your refactorings:
Group by Project: Refactorings are grouped by project. Every refactoring is associated with the project that contains the element which served as input to the recorded refactoring.
Note: There are certain instances of refactorings which cannot be uniquely associated with a project. These refactorings are associated with the entire workspace.
Group by Date: Refactorings are grouped by date. The refactoring history dialog presents the refactorings as a history, last recently executed refactorings first.
</dd>
<dt><br>Available for :</dt>
<dd>Any projects, folders and files regardless of project kind</dd>
</dl>

View file

@ -8,30 +8,74 @@
</head>
<body>
<h1>C/C++ Project Properties, Resource</h1>
<p>Shows resource information for the selected type.</p>
<br>
<p><img img="" src="../images/prop_resource.png"
alt="C/C++ Project Properties, Resource"></p>
<dl>
<dt>Resource</dt>
<dd>Shows resource information.</dd>
<dt>Text file encoding</dt>
<dd>Sets an alternate text encoding.</dd>
<dt>New text file line delimiter</dt>
<dd>Specifies the line delimiter.</dd>
<dt><br>Available for :</dt>
<dd>Any projects, folders and files regardless of project kind</dd>
</dl>
<p></p>
<table cellpadding="5" cellspacing="0" border="1" >
<br>
<caption><b>Resource properties</b></caption>
<br>
<colgroup>
<col width="30%" valign="top" >
<col width="70%" valign="top" >
</colgroup>
<tbody>
<tr>
<td><dt>Path</dt></td>
<td>Specifies the location of the selected resource type within the workspace. For example, similar to folders, projects map to directories in the file system.</td>
</tr>
<tr>
<td><dt>Type</dt></td>
<td>Indicates the type for the selected resource: <b>Folder</b>, <b>Project</b>, or <b>File</b>.</td>
</tr>
<tr>
<td><dt>Location</dt></td>
<td>Specifics the location of the selected resource within the file system.</td>
</tr>
<tr>
<td><dt>Last modified</dt></td>
<td>Shows the date that the selected resource was last modified.</td>
</tr>
<tr>
<td><dt>Text file encoding</dt></td>
<td>Sets an alternate text encoding. Because text files are encoded differently (depending on the locale and platform), use the default text file encoding for the locale of your host operating system. However, if you want to work with text files that originate from another source (for example, to work with text files that use a different encoding scheme than your native one, so that you can easily exchange files with another team), choose <b>Other</b> and select an appropriate one from the list.</td>
</tr>
<tr>
<td><dt>Inherited from container</dt></td>
<td>When enabled, the selected resource inherits the text encoding specified for it's container resource.</td>
</tr>
<tr>
<td><dt>Other</dt></td>
<td>When enabled, the selected resource uses an alternate text encoding other than that specified for its container resource. You can enable this option if you want to work with text files that originate from another source (ones that use a different encoding scheme than your native one), so that you can easily exchange files with others.</td>
</td>
</tr>
<tr>
<td><dt>New text file line delimiter</dt></td>
<td>Specifies the end of line character(s) to use for new text files being created.</td>
</tr>
<tr>
<td><dt>Inherited from container</dt></td>
<td>When enabled, the selected resource inherits the character line ending for new text files from that specified for it's container resource.</td>
</tr>
<tr>
<td><dt>Other</dt></td>
<td>When enabled, the selected resource uses an alternate end of line character(s) for new text files other than that specified for its container resource. For example, you can set the <b>Text file encoding</b> option to UTF-8, and then set the line endings character for new files to <b>Unix</b>, so that text files are saved in a format that is not specific to the Windows operating system, and the files can easily be shared amongst various developer systems.</td>
</td>
</tr>
</tbody>
</table>
<br>
<p><b>Available for:</b> Any projects, folders and files regardless of project kind.</p>
<p><img border="0" src="../images/ngref.gif" alt="Related reference"
width="143" height="21"><br>
<ul>
<li><a href="cdt_u_prop_resource.htm">Project Properties, Resource page</a>
<li><a href="cdt_u_prop_builders.htm">Project Properties, Builders page</a>
<li><a href="cdt_u_prop_all.htm">Project Properties, common C/C++ Configurations handling</a>
<ul type="disc">
<li><a href="cdt_u_prop_manage_dialog.htm">Manage Configurations dialog</a>
<li><a href="cdt_u_prop_manage_newdialog.htm">Create Configuration dialog</a>
<li><a href="cdt_u_prop_manage_rendialog.htm">Rename Configuration dialog</a>
</ul>
<li><a href="cdt_u_prop_build.htm">Project Properties, C/C++ Build category</a>
<ul type="disc">
<li><a href="cdt_u_prop_build_discovery.htm">Discovery options page</a>
@ -50,13 +94,6 @@
<li>Project Properties, C/C++ General category
<ul type="disc">
<li><a href="cdt_u_prop_general_doc.htm">Documentation page</a>
<li><a href="cdt_u_prop_general_exp.htm">Export Settings page</a>
<!--ul>
<li><a href="cdt_u_prop_general_exp_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_exp_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_exp_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_exp_libpath.htm">Libraries path tab</a>
</ul-->
<li><a href="cdt_u_prop_general_typ.htm">File Types page</a>
<li><a href="cdt_u_prop_general_idx.htm">Indexer page</a>
<li><a href="cdt_u_prop_general_lng.htm">Language Mapping page</a>
@ -64,15 +101,15 @@
<ul>
<li><a href="cdt_u_prop_general_pns_inc.htm">Includes tab</a>
<li><a href="cdt_u_prop_general_pns_sym.htm">Symbols tab</a>
<li><a href="cdt_u_prop_general_pns_lib.htm">Libraries tab</a>
<li><a href="cdt_u_prop_general_pns_libpath.htm">Libraries path tab</a>
<li><a href="cdt_u_prop_general_pns_src.htm">Source Location tab</a>
<li><a href="cdt_u_prop_general_pns_out.htm">Output Location tab</a>
<li><a href="cdt_u_prop_general_pns_ref.htm">References tab</a>
<li><a href="cdt_u_prop_general_pns_hier.htm">Data Hierarchy tab</a>
</ul>
</ul>
<li><a href="cdt_u_prop_ref.htm">C/C++ Project Properties, Project References page</a>
<li><a href="cdt_u_prop_refactoring_history.htm">C/C++ Project Properties, Refactoring History
page</a>
<li><a href="cdt_u_prop_rundebug.htm">C/C++ Project Properties, Run/Debug Settings page</a>
</ul>
</p>

View file

@ -15,10 +15,10 @@
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_proj_build_set.htm">Defining build settings</a><br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_proj_error_parser.htm">Filtering errors</a><br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_proj_parser.htm">Selecting a binary parser</a><br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_proj_paths.htm">Adding Include paths and symbols</a><br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_proj_paths.htm">Adding include paths and symbols</a><br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_proj_platf.htm">Selecting a project type</a><br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_manualbuild.htm">Building Manually</a><br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_autobuild.htm">Removing Build Automatically</a><br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_manualbuild.htm">Building manually</a><br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_autobuild.htm">Removing the <b>Build Automatically</b> setting</a><br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_autosave.htm">Autosaving on a build</a><br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_addmaketarget.htm">Creating a make target</a><br>
<img src="../images/trans.gif" border="0" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_t_cbuild_pref.htm">Customizing the Console view</a><br>

View file

@ -7,9 +7,9 @@
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<h1>Removing Build Automatically</h1>
<p>The Eclipse workbench is configured to build projects automatically.
However, for C/C++ development you should turn this feature off,
<h1>Disabling the Build Automatically option</h1>
<p>By default, the Eclipse workbench is configured to build projects automatically.
However, for C/C++ development you should disable this option,
otherwise your entire project will be rebuilt whenever, for example,
you save a change to your makefile or source files.
Click <b>Project &gt; Build Automatically</b> and ensure there is no

View file

@ -8,30 +8,30 @@
</head>
<body>
<h1>Set Discovery Options</h1>
<p>For most make projects, you will want to parse the output of
<p>For most <b>make</b> projects, you will want to parse the output of
the build to populate your paths and symbols tables. </p>
<p>To do so:</p>
<p><b>To populate your tables:</b></p>
<ol>
<li>Right-click on a project and select <b>Properties</b>.
<li>Expand <b>C/C++ Build</b> and select <b>Discovery Options</b>.
<li>Expand <b>C/C++ Build</b> and select <b>Discovery options</b>.
<li>Select the <b>Automate discovery of paths and symbols</b> option so that it is enabled.
<li>For the scanner configuration on the Discovery Options page of the C/C++ Properties window, you have the following options:
<p>There are currently three discovery profiles available on a <b>Per project</b> basis - all discovered paths and symbols are associated with the project; all files use this information. <br>
<p>There are various discovery profiles available on a <b>Per project</b> basis - all discovered paths and symbols are associated with the project; all files use this information. <br>
<dl>
<dt>Enable generate scanner info command</dt>
<dd>Enables the retrieval of information from the scanner.</dd>
</dl>
<p></p>
<div style="margin-left: 40px;"><img
alt="C/C++ Project Properties, Standard, Discovery Options"
src="../images/sprop_make_discovery_file.png"
style="width: 598px; height: 585px;"><br>
<div style="margin-left: 40px;"><br><img
alt="C/C++ Project Properties, Discovery Options"
src="../images/dprop_make_discovery_file.png" style="width: 1133px; height: 745px;"><br>
</div>
<p>For both profiles there is an option to discover paths and symbols
based on a previous build output. To activate the discovery select a
build log file and then the <span style="font-weight: bold;">Load</span>
<br>
<p>For both profiles, there is an option to discover paths and symbols
based on a previous builds' output. To activate the discovery, click <b>Browse</b> to select a
build log file, and then click the <span style="font-weight: bold;">Load</span>
button.<br>
</p>
</ol>