Program "<unused>" not found in PATH

[Joe C]

I opened a cmake based program in Eclipse CDT with cmake4eclipse on Ubuntu 20.04. The cmake build completed with no errors and I am able to debug and execute the build. But, I’ve got a little red 'x' on the project root in Project Explorer. In the Problems tab it has a single error: 'Program "<unused>" not found in PATH'

Searching the Project Properties, the only thing I found with an '<unused>' artifact was in C/C++ Build -> Settings -> Tool Settings. There is a single item – 'CMake driven Languages Proxy'. Next to that is 'Command: <unused>'. Below that, is 'Expert settings: Command line pattern: <unused>'

Did I miss a step? What doe the problem error mean and how do I get rid of it?

[Martin Weber]

On Mittwoch, 17. März 2021 10:23:45 CET Joe C wrote:
> I opened a cmake based program in Eclipse CDT with cmake4eclipse on Ubuntu
> 20.04. The cmake build completed with no errors and I am able to debug and
> execute the build. But, I’ve got a little red 'x' on the project root in
> Project Explorer. In the Problems tab it has a single error: 'Program
> "<unused>" not found in PATH'
>
> Searching the Project Properties, the only thing I found with an '<unused>'
> artifact was in C/C++ Build -> Settings -> Tool Settings. There is a single
> item – 'CMake driven Languages Proxy'. Next to that is 'Command: <unused>'.
> Below that, is 'Expert settings: Command line pattern: <unused>'

The reason why cmake4eclipse fills in the '<unused>' in the tab is to tell
users that the value entered is *actually* not used for building since cmake
itself controls the tools used for building.

>
> Did I miss a step? What doe the problem error mean and how do I get rid of
> it?

I have never seen that error before. Which CDT version do you use?
I have no clue why CDT wants to look up the <unused>-tool in PATH. Maybe the
problem type can give an indication.
To get rid of the error, you could try to clear the <unused> entries in the
tool settings tab.

Martin
--
Cd wrttn wtht vwls s mch trsr.

[Joe C]

@Martin, thanks for your reply. Your inquiry about the problem type clued me to take a closer look at the Problems panel. BTW, I'm using CDT 10.1.0 and the Problem Type was 'C/C++ Scanner Discovery Problem'. While searching for the latter I found that the problem Location and Type information was far off the end of the Problems panel display. I had to drag the fields into view.

I also found that I could get rid of error displayed in the panel by right-clicking it in the description field and select 'Delete'. After re-indexing, cleaning and rebuilding the project I verified the Problem entry did not return. I guess it was a residue from an earlier build when learning to set up the cmake4eclipse project.

The problem is resolved.