Build Settings

Build options settings

• Target Deployment Port: This setting allows you to override the TDP of the entire configuration for a specific node. Use this for example if you are mixing different languages or compilers within a single project. Any child nodes will use the default Configuration Settings from this Target Deployment Port, such as compilation flags. When you change the TDP within a Configuration, the settings are overwritten using the default settings of the new TDP.

• Build options: Build options allow you to specify how the test is built and executed. This is also where you enable the Runtime Analysis tools. See Selecting Build Options for a Node.

• Environment variables:This section allows you to specify any environment variables that can be used by the application under test. Click the "..." button to edit environment variables. String values must be entered with quotes ("").

  You can enter GUI macro variables as values for environment variables. These will be interpreted by the GUI and replaced with the actual values for the current node. SeeGUI macro variables.

• Ignored files (for Eclipse CDT only):Specifies a list of files that are ignored by the instrumentor. Click the ... button and use the Add and Remove buttons to select the files to be excluded.

• Instrumented files (for Eclipse CDT only):Specifies a list of files that are to be explicitly instrumented. Any other files are ignored.Click the...button and use theAddandRemovebuttons to select the files to be excluded.

• Clean result history:SelectYesto clear results before the application starts. This ensures that displayed results are for the last execution only.

• L ist tested files versions: Select the configuration management tool to be used to handle file versioning in the test report.

Compiler settings

• Assembler flags: Specify any additional command line options to be sent to the assembler for assembler source files.

• Preprocessing-only flags: Specific compilation flags used only for preprocessing. If no preprocessing is performed, these flags are used as compiler flags.

• Preprocessor flags: Specific compilation flags to be sent to the compiler.

• Compiler flags: Specify any additional command line options to be sent to the compiler.

• Preprocessor macro definitions: Specify any macro definition that are to be sent to both the compiler preprocessor (if used) and the Test Script Compilers. Several generation conditions must be separated by a comma ',' with no space. You can use a comma inside a condition, preceded a backslash character. For example:

semTake(x\,y)=TestRTsemTake(x\,y),WIN32,_DEBUG

• Default include directories: Use this setting to specify include directories that are specific to the current TDP (if you change the TDP, these directories will be lost). Click the ... button to create or modify a list of directories for included files when the include statement is encountered in source code and test scripts. In the directory selection box, use the Up and Down buttons to indicate the order in which the directories are searched.

• User include directories: Use this setting to specify include directories that are independent of the current TDP (if you change the TDP, these directories will be retained). Click the ... button to create or modify a list of directories for included files when the include statement is encountered in source code and test scripts. In the directory selection box, use the Up and Down buttons to indicate the order in which the directories are searched.

• User link file (for Ada only): When using the Ada Instrumentor, you must provide a link file. See Ada Link Files for more information.

Linker settings

This area contains parameters to be sent to the linker during the build of the current node.

• Additional objects or libraries: A list of object libraries to be linked to the generated executable. Enter the command line option as required by your linker. Please refer to the documentation provided with your development tool for the correct syntax.

• Library path:Click the ... button to create or modify a list of directories for library link files. In the directory selection box, use the Up and Down buttons to indicate the order in which the directories are searched.

• Link flags: Flags to be sent to the linker.

• Test driver filename : The name of the generated test driver binary. By default, HCL OneTest™ Embedded uses the name of the test or application node.

Execution settings

These settings apply to Component Testing and System Testing nodes only.

• Command line arguments:Specifies any command line arguments that are to be sent to the application under test upon execution.

• M ain procedure (for Ada only):Ada requires an entry point in the source code.

Target Deployment Port build settings

This area relates to the parameters of the Target Deployment Port on which is based the Configuration:

• Output buffer size:Sets the size of the output buffer. A smaller output buffer can save memory when resources are limited. A larger buffer improves performance.

  The default setting for the output buffer is1024bytes.

• Time measurement:Selects between a real-timeOperating system clockor aProcess or task clockfor time measurement, if both options are available in the current Target Deployment Port. Otherwise, this setting is ignored.

• Multi-threaded application:This box, when selected, protects Target Deployment Port global variables against concurrent access when you are working in a multi-threaded environment such as Windows. This can cause an increase in size of the Target Port as-well-as an impact on performance, therefore select this option only when necessary.

• Multi-processed application:When selected, this option produces a different output file for each process in forked applications.

• Maximum number of threads:When the multi-thread option is enabled, this setting sets the maximum number threads that can be run at the same time by the application.

• Override compiler flags:By default, the TDP is compiled with the build compiler flags. Use this setting to override the Build compiler flags with specific flags for compiling the TDP.

• TDP output format:This setting specifies how the TDP is linked to the application.

• • None:No TDP is generated. Use this setting if the TDP is already included in another section of the application.

  • Object file (.obj, .o):Default setting. Use this setting if your application does not use shared libraries.

  • Static library (.lib, .a):Use this setting to link the TDP as a static library.

  • Dynamic library (.dll, .so):Use this setting to link the TDP as a dynamic library for most cases when shared libraries are involved.

• Link flags for library format (for library nodes only):Link flags for generating the TDP as a shared library or DLL.

• Use source compiler flags (for Eclipse only):SelectYesto use the source build compiler flags to compile the test driver. SelectNoto use the default TDP settings.

• Use of unloadable libraries:Use the setting if your application uses shared libraries that can be unloaded dynamically from memory. See Unloadable libraries for details.

• • None:The application does not dynamically unload libraries during execution.

  • This is an unloaded library:Select this if the selected node is a library node that can be dynamically unloaded during execution.

  • Uses unloaded libraries:Select this if the selected node is an application or test node that can use unloadable libraries.

To edit the Build settings for a node:

1. In theProject Explorer, click theSettings button.

2. Select a node in theProject Explorerpane.

3. In theConfiguration Settingslist, expandBuild.

4. SelectCompiler,Linker,ExecutionorTarget Deployment Port.

5. When you have finished, clickOKto validate the changes.

Related Topics

Configuration Settings