-Customizes your build configuration command and output settings.
-
-
-
-
Project Type:
-
Displays the type of project that is built by the selected build
-configuration.
-
Configuration:
-
Specifies the selected build configuration from the list provided.
-
Manage...
-
Adds, removes, renames and converts configurations.
-
Configuration Settings, Build Settings
-
Sets the build command, build flags, the name of the build goal,
-whether to expand build environment macros in the generated make
-file, and whether to use the Internal Builder.
-
Restore Defaults
-
Returns any changes back to their default setting.
-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.
-
-
-
-
Project Type:
-
Displays the type of project that is built by the selected build
-configuration.
-
Configuration:
-
Specifies the selected build configuration from the list provided.
-
Manage...
-
Adds, removes, renames and converts configurations.
-
Pre-build Step
-
Command
-
Specifies a command, or a list of semicolon separated commands,
-to be executed immediately prior to execution of the build.
-
Description
-
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.
-
Post-build Step
-
Command
-
Specifies a command, or a list of semicolon separated commands,
-to be executed immediately after the execution of the build.
-
Description
-
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.
-
Restore Defaults
-
Returns any changes back to their default setting
-
Apply
-
Applies any changes.
-
-
-
Detailed Specification
-
To ensure reasonable custom build step behavior, sensible input must
-be provided when specifying custom build step input. Custom build steps
-are not verified for correctness in any regard and are passed exactly
-as entered into the build stream.
-
-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
-including pre-build or post-build steps.
-
-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.
-
-
-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.
-Customizes the environment variables to be used in building your build
-configuration.
-
-
-
-
Project Type:
-
Displays the type of project that is built by the selected build
-configuration.
-
Configuration:
-
Specifies the selected build configuration from the list provided.
-
Manage...
-
Adds, removes, renames and converts configurations.
-
Configuration Settings
-
Adds, removes and edits environment variables for a project or
-configuration. Each tab contains two tables - one for
-user-defined environment variables and one for non user-defined
-environment variables. Each table contains two columns:
-
Name of the environment variable
-
Value of the environment variable.
-
You can view all environment variables that are not user-defined
-in the System Variables table.You
-can choose to also display all variables defined for lower-precedence
-contexts in the System Variables table by checking the Show
-parent level variables checkbox. System variables are read-only.
-
You can view all user-defined variables in the
- User Variables table. A user-defined variable overrides a non user-defined
-variable of the same name for the given level. Overridden
-variables are displayed in bold in the System Variables table.
-
-
Restore Defaults
-
Returns any changes back to their default setting.
-
Apply
-
Applies any changes.
-
-
Detailed Specification
-
Users and tool-chain
-integrators can define the set of environment variables to be used
-while the build process is executing.
-
Since
-the environment variable names are case sensitive on Unix-like systems
-and case insensitive on Windows systems, the Managed Build System (MBS)
-will treat the variable names in the same manner as the host system.
-
-
-
MBS
-will allow tool-integrators and users to specify multiple variables
-whose names differ only in case on systems that support case sensitive
-variable names and will not allow them to do that on Windows systems.
-
-
-
MBS
-will also treat variable names as case sensitive (on Unix-like systems)
-or case insensitive (on Windows systems) in its own operations
-(overriding a lower-level variable, etc.)
-
-
-
Build Environment variables can
-be specified at several levels:
-
-
1.
- Configuration level – variables specific to the selected
-configuration
-
- 2.
-Project level – variables specific to the selected project and
-common for all project configurations
-
- 3.
- Workspace level – variables specific to the current workspace
-
- 4.
- System environment passed to eclipse
-
-
When running the build utility
-for the selected configuration, the process' total environment
-variables set will be generated, including variables from all specified
-levels. Levels have precedence over each other as specified in the
-above list. So, for example, if configuration level and workspace level
-have a variable of the same name, the configuration variable will take
-precedence, etc.
-
Users can create and delete environment
-variables for any given project configuration, for the entire project
-or for the entire workspace.
-
To create a new variable the "New"
-button should be pressed. A dialog box representing the variable
-definition will appear.
-
-
-
-
-
A variable definition contains the name,
-the value, the delimiter and the "operation" to
-perform on the variable of the same name defined at the
-lower-precedence level. The following "operations" are defined:
-
-
-
-"append": If the variable
-already exists, add the user-specified value to the end of any existing
-value that the environment variable has. If the variable does not
-yet exist, create the variable and set it to the user-specified value.
-
-
-
-"prepend": If the variable
-already exists, add the user-specified value to the beginning of any
-existing value that the environment variable has. If the variable
-does not yet exist, create the variable and set it to the
-user-specified value.
-
-
-"replace": If the variable
-already exists, set the value to the user-specified value. If the
-variable does not yet exist, create the variable and set it to the
-user-specified value.
-
-
-"delete": If the variable
-already exists, remove the variable.
-
-
The resulting value of the variable used for the build process will
-be calculated by querying all levels from bottom to top and performing
-the operations for the variables defined at those levels.
-
The "Name" field contains the list of variables that are already
-defined. A user can choose any variable from the list or enter a new
-variable name. When the variable from the list is chosen or the name
-typed by the user matches already defined variable name, the other
-fields of the dialog get filled in with the current value, delimiter
-and operation of that variable.
-
When the "replace" operation is selected, the "Value" field is used
-to specify the variable value.
-
When either the "prepend" or "append" operation is selected, the
-"Value" field becomes grayed and the "Prepended/Appended value" field
-becomes visible that allows user to specify the value to be
-prepended/appended. The resulting variable value will be automatically
-calculated and displayed in the "Value" field. The delimiter to be used
-with append/prepend operations may be specified in the "Delimiter"
-field.
-
-
-
When the "delete" operation is selected, the "Value", "Delimiter"
-and "Prepended/Appended value" field becomes inaccessible.
-
When performing the variable value calculation the variable name
-case sensitivity will be taken in account. That is, on Windows systems,
-the variables of the different levels or provided by different
-suppliers with names that differ only in case will be treated as the
-same variable. Conversely, on Unix-like systems, where case sensitive
-variable names are supported, variables with names that differ only in
-case will be treated as different variables.
You can select which C/C++ Indexer to use for your project. The
-indexer is necessary for search and related features, like content
-assist.
-
-
-
-
Available Indexers
-
Specifies the Indexer to use for this project; No Indexer
-disables indexing. Some indexers will display additional options below
-the indexer selection box.
-
Restore Defaults
-
Returns any changes back to their default setting.
-Customizes the build macros used in your build configuration.
-
-
-
-
Project Type:
-
Displays the type of project that is built by the selected build
-configuration.
-
Configuration:
-
Specifies the selected build configuration from the list provided.
-
Manage...
-
Adds, removes, renames and converts configurations.
-
Configuration Settings
-
Adds, removes, edits and manages build macros for a project or
-configuration.
-Each tab contains two tables - one for user-defined build macros and
-one for non user-defined build macros.
-Each table contains three columns:
-
-
-
-
Name of the build macro
-
Type of value contained in the build macro (see below)
-
Value of the build macro.
-
-
-
-
-
You can view all build macros that are not user-defined in the System
-Macros table. You
-can choose to also display all macros defined for lower-precedence
-contexts in the System Macros table by checking the Show
-parent context macros checkbox. System macros are read-only.
-
You can view all user-defined macros in the User
-Macros table.
- A user-defined macro overrides a non user-defined macro of
-the same name for the given context. Overridden macros are
-displayed in bold in the System Macros table.
-
-
-
-
Restore Defaults
-
Returns any changes back to their default setting.
-
Apply
-
Applies any changes.
-
-
Detailed Specification
-
Build Macros can be used in all C/C++ Build configuration properties
-that accept text. Build Macros are referenced in strings by enclosing
-them in braces, preceded by a dollar sign.
-There are no special restrictions on a macro name, though it is
-encouraged that a macro name begin with a letter and contain only
-letters, digits and underscore signs. Build macro names are case
-sensitive.
-
-If the actual value of text property contains ${text},
-it must be pre-pended with a backslash in order to distinguish it from
-a build macro. The Managed Build System (MBS) pre-defines many useful
-macros (see below) and allows tool integrators and users to define
-additional macros.
-
Build Macros can hold several types of values:
-
-
-
Text value: can be any text string
-
Text-List value: an array of Text values
-
Path-file value: can hold a file path
-
Path-dir value: can hold a directory path
-
Path-any value: can hold both a file and directory path
-
Path-file-List value: an array of Path-file values
-
Path-dir-List value: an array of Path-dir values
-
Path-any-List value: an array of Path-any values
-
-
Build Macros are context-sensitive, that is the
-macro of a given name could have different values depending on where it
-is used. Several contexts are defined:
-
-
-
The currently selected file.
-
-
-
The currently
-selected option
-
-
-
The currently
-selected configuration (which includes a tool-chain).
-
-
-
The currently
-selected project.
-
-
-
The current
-workspace.
-
-
-
The CDT and Eclipse
-installations.
-
-
-
The process
-environment variables defined in the environment passed to Eclipse.
-
-
-
Users can define and delete macros for any given
-project configuration, for the entire project or for the entire
-workspace.
-
The value of a build macro will be searched for in
-the order specified above. If macro is not found for the currently
-selected file context, the currently selected option context will be
-used, if not found, the currently selected configuration context will
-be used, etc. It is possible, but not recommended, for a
-user-defined macro to override the definition of an MBS pre-defined
-macro. Overriding MBS pre-defined macros can have unanticipated
-consequences.
-
To define a new macro the "New" button should be
-pressed. A dialog will appear representing the macro definition.
-
-
The "Name" field contains the list of macros that are already
-defined. A user can choose any variable from the list or enter a new
-variable name. When a macro from the list is chosen or the name typed
-by the user matches an already existing macro name, the other fields of
-the dialog get filled with the value, and value type of that macro.
-
When any of the "String," "File," "Directory" or "File or Directory"
-value types is selected, the macro value may be specified with the
-"Value" edit-box. For the "File" and "Directory" types, a "Browse"
-button is also displayed that allows selecting file or directory using
-the "Browse" dialog.
-
When either of the "List of Strings," "List of Files," "List of
-Directories" or "List Files or Directories" value types is selected,
-the macro value may be specified with the "Macro Value" multi-line text
-box and button bar.
-
-
-
-
Macro resolution takes place when the build file
-is being generated.
The Managed Build System pre-defines many useful
-macros described in the following tables:
-
File-specific macros
-
The set of file-context macros is predefined by
-the Managed Build System (MBS). Neither a tool-integrator nor a user
-can define new file-context macros.
-
-
-
-
-
Macro
-
-
-
Value
-Type
-
-
-
Description
-
-
-
-
-
${InputFileName}
-
-
-
Text
-
-
-
Represents the
-input file name. The input file has the following meaning:
-
1.
- If a tool does not accept building multiple files of the
-primary input type with one tool invocation, the input file is the file
-of the primary input type being built.
-
2.
- If a tool accepts building multiple files of the primary
-input type with one tool invocation the input file is undefined and the
-macros representing the input file contain information about one of the
-inputs of the primary input type being built.
-
-
-
-
-
${InputFileExt}
-
-
-
Text
-
-
-
Represents the
-extension of the input file.
-
-
-
-
-
${InputFileBaseName}
-
-
-
Text
-
-
-
Represents the
-base name of the input file. That is the file name with an extension
-stripped.
-
-
-
-
-
${InputFileRelPath}
-
-
-
Path(File)
-
-
-
Represents the
-input file path relative to the builder current directory.
-
-
-
-
-
${InputDirRelPath}
-
-
-
Path(Dir)
-
-
-
Represents the
-input file directory path relative to the builder current directory.
-
-
-
-
-
${OutputFileName}
-
-
-
Text
-
-
-
Represents the
-output file name. The output file has the following meaning:
-
1.
- If a tool is not capable of producing multiple files of
-the primary output type with one tool invocation the output file is the
-file of the primary output type that is built with a given tool
-invocation.
-
2.
- If a tool is capable of producing multiple files of the
-primary output type with one tool invocation the output file is
-undefined and the macros representing the output file contain
-information about one of the files of the primary output type that are
-built with a given tool invocation.
-
-
-
-
-
${OutputFileExt}
-
-
-
Text
-
-
-
Represents the
-output file extension.
-
-
-
-
-
${OutputFileBaseName}
-
-
-
Text
-
-
-
Represents the
-output file base name. That is the output file name with an extension
-stripped.
-
-
-
-
-
${OutputFileRelPath}
-
-
-
Path(File)
-
-
-
Represents the
-output file path relative to the current builder directory.
-
-
-
-
-
${OutputDirRelPath}
-
-
-
Path(Dir)
-
-
-
Represents the
-output file directory path relative to the current builder directory.
-
-
-
-
-
Configuration-specific
-macros
-
-
-
-
-
Macro
-
-
-
Value
-Type
-
-
-
Description
-
-
-
-
-
${ConfigName}
-
-
-
Text
-
-
-
Represents the
-name of a given configuration.
-
-
-
-
-
${ConfigDescription}
-
-
-
Text
-
-
-
Represents the description of a given
-configuration.
-
-
-
-
-
${BuildArtifactFileName}
-
-
-
Text
-
-
-
Represents the name of the build artifact.
-
-
-
-
-
${BuildArtifactFileExt}
-
-
-
Text
-
-
-
Represents the extension of the build
-artifact.
-
-
-
-
-
${BuildArtifactFileBaseName}
-
-
-
Text
-
-
-
Represents the base name of the build
-artifact.
-
-
-
-
-
${BuildArtifactFilePrefix}
-
-
-
Text
-
-
-
Represents the prefix of the build artifact.
-
-
-
-
-
${TargetOsList}
-
-
-
Text-List
-
-
-
Represents the list of the target OS names.
-
-
-
-
-
${TargetArchList}
-
-
-
Text-List
-
-
-
Represents the list of the target Arch names.
-
-
-
-
-
Project-specific macros
-
-
-
-
-
${ProjName}
-
-
-
Text
-
-
-
Represents the
-name of a given project.
-
-
-
-
-
${ProjDirPath}
-
-
-
Path(Dir)
-
-
-
Represents the absolute path of a given
-project.
-
-
-
-
-
Workspace-specific
-macros
-
-
-
-
-
${WorkspaceDirPath}
-
-
-
Path(Dir)
-
-
-
Represents the workspace absolute path.
-
-
-
-
-
${DirectoryDelimiter}
-
-
-
Text
-
-
-
Represents the directory delimiter used on
-the system. That is the “\? for Win32 systems and the “/? for Unix-like
-systems
-
This could be useful, e.g. in the case a
-user needs the absolute path of an input file. The absolute path would
-be represented in the following way:
-${CWD}${DirectoryDelimiter}${InputFileRelPath}
-
-
-
-
-
${PathDelimiter}
-
-
-
Text
-
-
-
Represents the default path delimiter used
-on the system to separate paths in the path environment variables. That
-is the “;? for Win32 systems and the “:? for Unix-like systems
-
This might be used in the environment
-variable definitions
-
-
-
-
-
CDT/Eclipse installation-specific macros
-
-
-
-
-
${EclipseVersion}
-
-
-
Text
-
-
-
Represents the current Eclipse version.
-
-
-
-
-
${CDTVersion}
-
-
-
Text
-
-
-
Represents the current CDT version.
-
-
-
-
-
${MBSVersion}
-
-
-
Text
-
-
-
Represents the current MBS version.
-
-
-
-
-
${HostOsName}
-
-
-
Text
-
-
-
Represents the operating system name on
-which eclipse is running.
-
-
-
-
-
${HostArchName}
-
-
-
Text
-
-
-
Represents the architecture name on which
-eclipse is running.
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
-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.
-
-
-
Project Type:
-
Displays the type of project that is built by the selected build
-configuration.
-
Configuration:
-
Specifies the selected build configuration from the list provided.
-
Manage...
-
Adds, removes, renames and converts configurations.
-
Configuration Settings, Binary Parser
-
Specifies a binary parser from the list provided.
-
Restore Defaults
-
Returns any changes back to their default setting.
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).
+
+
Manage configurations
+
Adds, removes, renames configurations. Sets active configuration.
This page serves as holder for all builder-specific property pages.
+In addition, you can define settings for the Builder just on the place.
+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.
+
+
+
+
+
+
+
+
+
Builder type
+
Select either internal or external builder
+
Use default build command
+
Select this checkbox to use the default make command.
+ Clear the check box to specify a new make command.
+ Available for external builder only.
+
+
Build command
+
If you clear the Use default checkbox type a new make command in this field. Variables can be used.
+
+
Generate makefiles automatically
+
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).
+
+
+
Expand env variable refs in Makefile
+
Defines whether environment variables ( ${xxx} ) should be expanded in makefile. Usually yes.
+
+
Stop on first build error
+
Stops building when any error occurs.
+
+
Use parallel build
+
Check this box if you want to use parallel project build
+
+
Use optimal jobs number
+
If parallel build enabled, lets builder to choose appropriate jobs number.
+
+
Use parallel jobs
+
If parallel build enabled, defines jobs number explicitly.
+
+
Workbench Build Behavior
+
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.
+
+
Build directory
+
Defines place where build operation is performed. Disabled when Makefiles Generation is ON.
+Customizes the environment variables to be used in building selected configuration.
+
+
+
+
Environment variables to set
+
List of existing Eclipse-specific environment variables.
+ It is not the same as native environment variables list.
+ See details below.
+ User-defined variables are marked with bold font.
+
+
+
New...
+
Add new environment variable to the list
+
Select...
+
Add one or more native environment variable(s) to the list
+
Edit...
+
Change value of existing variable. If system variable is changed, it becames user's.
+
Remove
+
Removes selected variable. Note that some variables are read-only and cannot be removed.
+
Undefine
+
Clear variable's value but leave it present.
+
Append variables to native environment
+
Eclipse will be able to access both native environment and variables defined on this page.
+
Replace native environment with specified one
+
Eclipse will be able to access only variables defined on this page.
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
+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.
+
+
+
Binary Parser (left pane)
+
List of all binary parsers known to CDT.
+ Mark parsers you wish to use with checkmark.
+ Select corresponding line to edit parser's options, if any
+
'Move up' and 'Move down'
+
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.
+
+
Binary Parser Option
+
Parser-specific parameters. Different parsers may have different options list (in particular, they may have no options at all).
Customizes the list of the filters that detect error patterns in the
+build output log.
+
+
+
Error Parsers (left pane)
+
List of all error parsers known to CDT.
+ Mark parsers you wish to use with checkmark.
+ Select corresponding line to edit parser's options, if any
+
'Move up' and 'Move down'
+
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.
+
+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.
+
+
+
+
Pre-build Steps
+
Command
+
Specifies a command, or a list of semicolon separated commands,
+to be executed immediately prior to execution of the build.
+
Description
+
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.
+
Post-build Steps
+
Command
+
Specifies a command, or a list of semicolon separated commands,
+to be executed immediately after the execution of the build.
+
Description
+
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.
+
Available for :
+
CDT projects
+
+
+
Detailed Specification
+
To ensure reasonable custom build step behavior, sensible input must
+be provided when specifying custom build step input. Custom build steps
+are not verified for correctness in any regard and are passed exactly
+as entered into the build stream.
+
+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
+including pre-build or post-build steps.
+
+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.
+
+
+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.
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).
+
+
Manage configurations
+
Adds, removes, renames configurations. Sets active configuration.
You can modify the list of exported elements
+(include paths, symbols, libraries, library paths)
+
+
+
+
+
+There are 4 tabs on this page: Include paths, Symbols, Libraries, Library paths.
+
+They have the similar design and display corresponding
+elements exported by current project to outside.
+
+There are 2 ways to make value exported:
+
+
Use 'Add' button on Export page
+
Use 'Export' button on Path and Symbols page.
+
+
+
+
Add
+
Add new element
+
Edit
+
Modify selected element
+
Delete
+
Remove selected element
+
Available for :
+
CDT projects. May be enabled/diabled in Preferences.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_prop_general_idx.htm b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_prop_general_idx.htm
new file mode 100644
index 00000000000..6464bd2b8cc
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_prop_general_idx.htm
@@ -0,0 +1,91 @@
+
+
+
+
+
+ C/C++ Project Properties, Indexer
+
+
+
+
C/C++ Project Properties, C/C++ Indexer
+
You can select which C/C++ Indexer to use for your project. The
+indexer is necessary for search and related features, like content
+assist.
+
+
+
+
Enable project specific settings
+
Check this box if you need specific index settings for this project. Else common settings (defined in Preferences) will be applied. In this case, all controls below are disabled.
+
Select indexer
+
Specifies the Indexer to use for this project; No Indexer
+disables indexing. Every indexer may have its own set of options.
+
+
Build configuration for the indexer
+
Index source either from specified configuration, or from active one.
+ Since indexing takes a lot of time, using active configuration is not recommended,
+ because re-index will be fired after each active configuration change.
+
+
+
+
+
\ No newline at end of file
diff --git a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_prop_general_pns_ref.htm b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_prop_general_pns_ref.htm
new file mode 100644
index 00000000000..45ae16f936c
--- /dev/null
+++ b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_prop_general_pns_ref.htm
@@ -0,0 +1,94 @@
+
+
+
+
+
+ C/C++ Project, Paths and Symbols, Project References
+
+
+
+
C/C++ Project Properties, Paths and Symbols, Project References
+
+User can adjust references among CDT projects.
+Unlike Eclipse Common References page,
+current page allows setting references to specific configuration.
+
+
+
+
+
Projects list (main pane)
+
Displays all other CDT projects which current project can refer to.
+ All configurations are displayed for each project. Put check mark on
+ projects and configurations to make them referred. Note that only
+ one configuration can be checked. [Active] configuration presents
+ in each configs list and represents current active configuration.
+
Expand all
+
Expands all configuration lists
+
Show checked
+
Expands configuration lists for referred projects only.
+
+
+
+
+
+
+
-
-