This topic explains how to install the C/C++test plugin into a working copy of Eclipse or Linux system.
The section includes:
- One of the following platforms:
- Linux with glibc 2.12 or higher and an x86-compatible processor.
- Linux with glibc 2.12 or higher and an x86_64-compatible processor.
- 4 GB RAM (8 GB is recommended).
- A supported compiler or cross-compiler (see Supported Environments for a list of supported compilers)
Proper Compiler Configuration is Critical
In most cases, C/C++test needs to invoke the compiler and linker in order to perform static analysis and runtime testing tasks, which commonly involve preprocessing, compiling, and linking programs.
To access C/C++test’s full functionality, the machine where C/C++test is run must have the complete development environment and compiler tool chain.
- Eclipse IDE for C/C++ Developers and a Java Runtime Environment (JRE) supported by Eclipse
- Wind River Workbench
- ARM DS-5
- Texas Instruments Code Composer Studio
See IDE Support for details about supported versions.
Choose the Proper Plug-In Architecture
- 32-bit IDEs require 32-bit C++test
- 64-bit IDEs require 64-bit C++test
- All users must be able to write to the Eclipse configuration directory. If all users cannot write to the current Eclipse configuration directory, then the location of that directory must be changed. To change the directory location, open the
<Eclipse_Installation_dir>/configuration/config.inifile, then add a line of the format
[email protected]/EclipseConfigData(Be sure to enter the appropriate location.) This configures Eclipse to keep all its configuration data in the
$(HOME)/EclipseConfigDatadirectory. You must have full access rights to that location
- If earlier versions of C/C++test are installed on your system, the latest version of C/C++test must be installed in a fresh directory. Please install C++test in a different directory than the previous version installation, and then modify the PATH to point to the new installation.
- During installation, you need to have permission to write to the Eclipse installation directory.
- Additional disk space is required for C/C++test project data.
- The recommended Japanese language encoding is Shift_JIS (ja_JP.PCK locale on Unix). Other encodings might cause font problems or prevent C/C++test from reading test results.
- Installation scripts require that the working directory has write permissions.
Warning - Critical workaround for installations where some users have restricted write privileges
Known issues with the location of Eclipse configuration/cached data (https://bugs.eclipse.org/bugs/show_bug.cgi?id=54919) could prevent Eclipse from starting properly once C/C++test is installed.
To prevent this problem:
- Open the
<Eclipse_Installation_Dir>/configuration/config.inifile for editing.
- Add the following line (the actual directory name can be changed):
As a result, Eclipse should keep all its config data in
$(HOME)/EclipseConfigData directory (you miust have full access rights to that location).
For details on running multiple instances of Eclipse with C/C++test in parallel see Multi-user Installations.
Parasoft Test Components
C/C++test Professional includes Parasoft Test components that are common across a number of Parasoft products version 9.x. If you want to use C/C++test Professional and other Parasoft Test 9.x products on a single Eclipse installation, run C/C++test installation as described below and specify the same Eclipse installation directory as the other Parasoft Test products use.
If Parasoft Test is already installed, it will be upgraded to the latest version (if needed) during C/C++test installation.
To install the C/C++test plugin for Eclipse on Linux:
- Copy the distribution file to the target location.
- Because Linux does not have any restrictions on having multiple versions of the same software installed on the same machine, the best way to install C/C++test is to provide a separate directory for each version.
- For example, if your software is installed in /opt/app/, then the recommended installation directory configuration should be something like /opt/app/parasoft/cpptest-extension/<version>. Version 10.3 could be installed in /opt/app/parasoft/cpptest-extension/ 10.3/ and version 10.4 could be installed in /opt/app/parasoft/cpptest-extension/10.4/. This provides the safest, most intuitive, and most flexible installation structure. During the installation, you will be prompted to enter a destination location for C++test Extension and Parasoft Test Extension files; defaults will be "parasoft/cpptest-extension/<version>" and "parasoft/test-extension/<version>". In this case, the target location for the distribution file should be /opt/app.
- Unpack the installation script using the appropriate command(s):
tar -xf cpptest_<version>_<arch>.tar
- Execute the following command to run the installation script:
- Choose the appropriate Eclipse/CDT target platform type.
- Enter your Eclipse (or Development Suite) installation directory, then click OK.
- Choose the directory that contains .eclipseproduct.
If you later want to uninstall C++test:
- Go to the C/C++test installation directory.
extuninstallC/C++test will then be "unregistered" from Eclipse.
- (Optional) Remove C/C++test files from the hard drive.
Alternative installation methods
For details on performing a silent installation see Preconfiguration C++test During Installation.
Before launching C/C++test
To allow C/C++test to autodetect compiler and makefile settings, ensure that the necessary executables (compiler/linker, makefile, etc.) are correctly configured. "Correctly configured" means different things on different compilers, but it typically involves ensuring that the executable is on the PATH.
To launch the plugin:
- Launch Eclipse as normal.
Eclipse will automatically find the C/C++test plugin.
After Eclipse is launched, you should see a Parasoft menu added to the Eclipse menu bar. If you do not see this menu, choose Window> Open Perspective> Other, select
C++test, then click OK.
If you suspect that C/C++test is not properly installed, see Troubleshooting and FAQs for help resolving some common installation problems.
The license is configured through the centralized licensing framework (Parasoft> Preferences> Parasoft> Licenses). For details, see Licensing.