C++ (with Parasoft)

The Lattix Parasoft for C++ module takes the .ldi.xml files output from Parasoft C/C++test. Parasoft C/C++test has an available feature to output Lattix LDI files that can be read into Lattix for architectual processing. Parasoft produces a “deps” directory with all of the individual .ldi.xml files which can then be loaded into Lattix. If you are using the Lattix Architect GUI you can input the “deps” directory directly into Lattix.

Parasoft C/C++test Standard

These commands will generate the *.ldi.xml files from parasoft.

cpptestcli -compiler gcc_9-64 -config "builtin://Export Code Dependency Data" -input cpptestscan.bdf -module .

Parasoft C/C++test Professional

cpptestcli -data path_to_workspace -config "builtin://Export Code Dependency Data"  -localsettings local-settings  -appconsole stdout -bdf cpptestscan.bdf

* The path_to_workspace should point to an existing directory outside of the current directory. It is the eclipse workspace that will be used by Parasoft *

In Profressional, to control where the dependencies are in located, you can add a line to local-settings.

This specifies a link to another file named dependency.properties

cpptest.advanced.settings.file=dependency.properties

And the dependency.properties property file should specify the output directory

cpptest.analyzer.dependency.report.location=output_directory

To create a Lattix project from the the *.ldi.xml files, try this on the command line:

For Standard (the data created by Parasoft should be in the “reports” directory)

ldcupdate project_parasoft.ldz -module:parasoft deps:reports

For Professional

ldcupdate project_parasoft.ldz -module:parasoft deps:output_directory

The output_directory is the same directory specified in the dependency.properties file above