...
The following image shows the Create Test Project command for “Flexible” build support build targets:
The following image shows the Create Test Project command for “Standard” build support build targets:
The Create Test Project command starts the C++test wizard for Test Projects creation. This wizard consists of the following pages
...
Build commands are prefixed with the C++test utility designed to collect compiler/linker flags and store them in a build data file. For more details this utility, see Creating a Project Using an Existing Build System.
| Note | ||
|---|---|---|
| ||
When C++test attempts to collect build information, it starts the build process for all selected build targets and prefixes the compiler/linker/librarian command lines with the C++test utility that records the build flags. As a result, it’s very important to call “clean” on all included build targets before you involve the Create Test Project—or ensure that the make command line template for all included projects (parents for selected build targets) is modified as follows:
instead of default: You can make this modification upon project creation, or do it later in the Build command field in the Project Properties> Build Properties> Build Support tab. C++test can replace %makeprefix% with an arbitrary parameter. In order to obtain all build options from the Workbench build, C++test needs to execute make with the -B parameter. C++test execution of the Workbench build does not actually entail building binary files, since the compiler is replaced by C++test option scanning utility. In order to be able to attach the -B parameter to the make execution, having the build command as make %makeprefix% is most convenient, and does not cause any other changes in the standard Workbench build. |
...
C++test tries to link the parent folder of any source file that was included in the build process. Using this panel, you can modify the automatically-generated test project structure via shortcut (right-click) menus.
Project Contents Settings
...
Note that when the project is imported to another workspace, the applied variables need to be defined (through the Window> Preferences> General> Workspace> Linked Resources menu). Usually, the workspace location is referenced using a variable.
Refresh Test Project Command
...
The “Test Project References” property page allows you to change the set of build targets that are initially included when the test project is created. The property page is available through Project Properties > C++test > Test Project References.
The Property page contains a test project references table view with the list of build targets that are referenced by a test project. When you choose the Refresh Test Project command, C++test will try to collect build flag information for all the resources referenced in this list.
...
When a test project is created, C++test links to it all directories containing source files that were compiled while building the referenced build targets. This is a one-time activity and no additional automatic resource linking is done later, after the project is created. As a result, if you want to link a resource that was added after the original project creation, you need to add that link manually—using the standard Eclipse facilities for adding linked resources (New> File/Folder> Advanced, Link to file/folder in file system).
| Note | ||
|---|---|---|
| ||
We strongly recommend using linked resource rather than making copies of existing resources. |
...