Welcome to the new Parasoft forums! We hope you will enjoy the site and try out some of the new features, like sharing an idea you may have for one of our products or following a category.

Failure to execute make through cpptesttrace, wrong path to make

chalecampb
chalecampb Posts: 1 ✭
in C/C++test

Hi,

We have two environments in which the builds run, one is on an integration server, but also, the builds can be executed locally. Locally, the parasoft version is 2024.1, and on the server, it is 2023.2.0 (10.6.3.20231201B4159). The server is linux, the local is windows.

In the first case, we can wrap ${MAKE} with cpptesttrace and some options, and it works fine. It generates the BDF and we can then scan those files.

When we run the exact same makefile locally, Parasoft tries to find its own copy of make from some combination of local and environment variable paths. The command that fails is

${CPPTESTTRACE} --cpptesttraceOutputFile=${APPL_BDF_FILE} ${MAKE} -f ${SUPPLIER_PATH}/Makefile hwioappl

I would expect ${MAKE} to resolve to make, which is on the path (and it does so on our end). Once it gets into cpptesttrace, it is replaced by the following path, a little sanitized,

C:/Apps/Parasoft/CCppTest_Standard/cpptest/bin/cpptesttrace --cpptesttraceTraceCommand=dcc --cpptesttraceOutputFile=thing.bdf make -f Code/Makefile maketarget

/bin/sh: /c/GIT/27.27.179.2p0_AGG_ParasoftIntegration/C:/apps/opentoolsuite/runtime/msys_GitEcosystem/bin/make.EXE: No such file or directory

For some context, /c/GIT/27.27.179.2p0_AGG_ParasoftIntegration is the PWD, C:/apps/opentoolsuite/runtime/msys_GitEcosystem/bin is an environment variable called MSYS_HOME. It's not clear to me how cpptesttrace is generating the path to make, but it is incorrect. I also tried with --cpptestscanRunOrigCmd=yes and it is still doing the same thing (ie, not the original command shown above).

I thought maybe it was unable to find make and trying some fallback method to locate it, but, make is on the PATH anyway, so it's not clear how cpptesttrace would have lost that PATH copy. And we seem to have success on the server, but not local, so there is some behavioral difference.

Any assistance would be appreciated,

Thanks!
-Alex

Categories