Best Of

Hi @Novodes ,

First a couple remarks:

• From your output I see that you are running C/C++test Professional Edition v. 2021.1. The -compiler option is not valid for this edition (-compiler is used by C/C++test Standard Edition). With C/C++test Professional you need to have a project configured in your workspace. C/C++test configuration for the project, including compiler settings, is available in project properties and this is where you need to select your compiler. See here: https://docs.parasoft.com/display/CPPTESTPROEC20211/Setting+Project+and+File+Options
• Also, I would avoid running the tool under C:\Windows\system32 - this is folder of the operating system, and it is better not to do any work there. C/C++test may need to save some temporary data or output files in the current folder, so it is best to run it in a dedicated folder or in the folder of the project that you want to analyze.

Now, back to the -config option:
C/C++test can perform many types of analyses and tests. Therefore, in order to run C/C++test from command line, you need to tell C/C++test what it is exactly you want to do in particular run, and the means to do that is to specify test configuration via the -config option.
I assume here that you are familiar with the concept of C/C++test test configurations. If not, here is the relevant documentation page: https://docs.parasoft.com/display/CPPTESTPROEC20211/Concepts+and+Terms#ConceptsandTerms-TestConfigurations

List of built-in configurations for the latest C/C++test 2021.1 is here: https://docs.parasoft.com/display/CPPTESTPROEC20211/Built-in+Test+Configurations
You can also get it by running "cpptestcli -list-configs" (again "cpptestcli -help" to the rescue).

In your case, to run e.g. builtin flow analysis configuration, you would need to use -config option like this:
cpptestcli -config "builtin://Flow Analysis" <other cpptestcli options>

In some cases where runtime library during initialization needs to have some software/hardware components to be up and running and initialized prior to initialization. e.g.: RTOS.
By default: When collecting application level coverage, runtime library is being initialized as early as fist instrumented line of code is being executed. In order to NOT automatically initialize runtime you need to do the following:

1) Need to build runtime differently.

Add the CPPTEST_AUTO_INITIALIZATION=0 to the list of your macros during building runtime library:

$ make EXTRA_CFLAGS="-DCPPTEST_AUTO_INITIALIZATION=0"

2) need to add this trigger in code (e.g. right after OS_Init) to initialize parasoft runtime:

#include "cpptest.h"
CppTest_InitializeRuntime()

Hello,

I am using the CMake extension for creating C/C++ Test projects and what I noticed is, that the extension is also capturing commands which compile/link temporary files during a CMake build. This is especially, or maybe only, the case when the build has dependencies on other static libraries.

These commands will also make it into the bdf file, which in the end cause linking issues during test generation.

If I remove following entries from the bdf file, everything works as expected:

arg=--whole-archive
arg=CMakeFiles\MYAPPNAME.dir/objects.a

arg=--out-implib
arg=libMYAPPNAME.dll.a

Kind Regards
Konstantin