Local/Remote C/C++ Project Wizard - Service Providers

C/C++ Indexing Service

New Remote C/C++ Project Wizard - Page 3, C/C++ Indexing Service


Name Function
Enable Service Enable or disable the indexing service. Services are essentially well defined sets of functionality which can be provided by Service Providers.
Service Provider Service Providers provide implementations of a Service. Each service has a list of available providers. The RDT Remote C/C++ Indexing Service is selected by default. This feature parses your source code, analyzes its structure, and creates an index (database) of named entities in your code for fast lookups. The index stores information such as the relationships of declarations to their references, and location information. The RDT Remote C/C++ Indexing Service uses the Remote Systems Explorer's dstore protocol to access a server that you deploy on the remote machine where your project resides. The actual parsing and indexing are done on the remote machine in order to reduce network traffic, and only the results of the queries are sent back to populate the user interface.
Connection Host The remote machine where the parsing and indexing will be done.
Index Location The location where the index (database) of named entities is stored.

Build Service

New Remote C/C++ Project Wizard - Page 3, Build Service


Name Function
Enable Service Enable or disable the build service. Services are essentially well defined sets of functionality which can be provided by Service Providers.
Service Provider Service Providers provide implementations of a Service. Each service has a list of available providers. The Build Service represents the execution and file manipulation services required by a builder to execute external build commands on the target system. A builder is still required which utilizes the build service to execute the commands to perform the build. The RDT Remote Build Service provider is selected by default.
Provider The RDT Remote Build Service provider uses the PTP Remote Services API to provide build services. Currently there are two possible sub-choices for these services:
Connection The name of the connection that the provider has been configured to use.
Build Configuration Location The location where build configuration settings are stored.