Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space CPPTDESKDEV and version 10.3.4

Working with Tornado typically means developing applications for the VxWorks version which comes with the Tornado release (see the assignments detailed in Supported Tornado Versions and Compilers). However, you can also build for other VxWorks versions, or even for your own abstract platforms—as long as you mind the list of architectures for which you have Tornado tools installed (for the list of architectures, see the Tornado manual).

Ideally, C++test would be preconfigured to support any platform, regardless of the installed Tornado tools version. However, it’s not possible to predict all of the possible applications. Currently, C++test supports only those VxWorks operating systems that are officially distributed with Wind River Tornado/Workbench releases; the supported operating systems are listed in Known Limitations

This means that C++test itself (without additional external configuration updates/modifications) restricts the number and type of platforms for which it may build the Test Object, but still lets you choose among them. In other words, although Tornado-2.0 comes with VxWorks-5.4 and Tornado-2.2 with VxWorks- 5.5, you can also test newer versions of VxWorks—as long as they are compatible with your Tornado version.

Specifically, if you are testing for VxWorks following the default path offered by C++test, you need to have the "__VXWORKS__" compilation macro present in order to perform either Static Analysis or Unit Testing. To add this macro, open the C++test Project Properties panel, go to the Build Settings> Options> Compiler options field, then append it there (for example: " -D__VXWORKS__ ").

If you plan on performing unit testing, the test object also has to be linked against the C++test runtime library. By default, it is built in one of the test flow steps. However, you can still build and link it manually if needed (for details, see Working with the C++test Runtime Library). If you do decide to build and link the runtime manually (e.g., because you require customization), you need to append a path to the built C++test runtime library artifact in the Linker options field in the C++test Project Properties panel’s Build Settings> Options area.

You can enter other custom options into these fields if desired.

titleNote on the "__VXWORKS__" macro

Most of the Wind River tool chains define this macro internally. If you know that your tool chain version does this, then you can skip this macro in configuration. However, this macro is missing in tool chains from our supported releases of Wind River Tornado (2.0.x, 2.2)