diff -r 000000000000 -r fb279309251b core/com.nokia.carbide.cpp.doc.user/html/reference/indexer.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/indexer.html Fri Apr 03 23:33:03 2009 +0100 @@ -0,0 +1,68 @@ + +Indexer + + + +

Indexer

+

The C/C++ indexer uses the parser to create a database of your source and header files that provides the basis for C/C++ search, navigation features and content assist. The goal of indexing is to record all named elements in a project's source code and store them with their related data. The indexer parses each source file in your project and updates related indexes. By indexing your files with the indexer, useful features such as code completion and fast file search can be used. It is also possible to specify different indexer settings for each project in your workspace.

+

If you choose to perform the Full C/C++ Indexer option the indexer will consume the CPU for some time, but you will gain more benefit from the process after it completes. + However, if you do not require the benefits of indexing your project, select the No Indexer option to speed up the process of building your project.

+

The indexer runs on a background thread and reacts to resource change events such as:

+ +

The Preferences Indexer can be accessed by selecting Window > Preferences then expanding the C/C++ group and selecting Indexer (figure 1). The Project Properties Indexer can be accessed by selecting a project in the C/C++ Projects or Symbian Project Navigator view and selecting Project > Properties, then select C/C++ Indexer (figure 2).

+

NOTE You can also rebuild a project's index by selecting a project, right-click to display the context menu and select Rebuild Index.

+

+

Figure 1 - Indexer Window in Preferences Panels

+

 

+

+

Figure 2 - Indexer Window in Project Properties

+

 

+ + + + + + + + + + + + + + + + + + +
NameFunction
Available indexers

Dropdown list of available index options.

+
    +
  • No Indexer - Project source files will not be indexed, therefore search features will not work accurately and code completion will not be available.
  • +
  • Fast C/C++ Indexer - Source files will be indexed and eat up a lot of CPU time and memory during the first generation of the indexer. This can take some time depending on the size of your project. Afterwards the indexer will only reindex the relevant parts you changed in your code and not the whole source tree.
  • +
  • Full C/C++ Indexer - Performs a complete parse of all source files and takes up the most amount of time to complete.
  • +
Apply indexer to all projects now Select this option to apply the Fast C/C++ Indexer option to all projects in your current workspace.
Rebuild the index when changing to a different build configuration Select this option to rescan and index the source files for the current project when you change the active build configuration. The index will be built based on the active build configuration. All macros and header files used to build the index will be taken from the active build configuration.

Build the index only for the build configuration specified in the project's indexer settings

+

 

+

Build the index only for the specified build configuration

The indexer will only be run for the build configuration specified in the Indexer panel in the project's property settings. All macros and header files used to build the index will be taken from the specified configuration.

+

 

+

NOTE This option appears in the project properties indexer panel. A dropdown list is provided to select a build configuration for the currently selected project.

+

 

+
Related concepts
+ +
Related tasks
+ + + + + + \ No newline at end of file