STM32CubeIDE: "Path Entry Problem" warnings that won't go away

cbcooper · ‎2026-03-12

It's telling me (for example) there's a "Path Entry Problem":

Invalid project path: Include path not found (C:\Users\xxx\Documents\xxx\USB_CDC\USB_Device\Target).

The Tool Settings / MCU GCC Compiler / Include paths contains

"${workspace_loc:/${ProjName}/Application/USB_Device/Target}"

and in my project there is a folder Application/USB_Device/Target, it links to a folder

C:\Users\xxx\Documents\xxx\USB_CDC\STM32CubeIDE\Application\USB_Device\Target

How can I figure out where this warning is coming from?

(notice - the project builds just fine, it's just a warning, but company policy is to build without warnings)

Andrew Neil · ‎2026-03-12

@cbcooper wrote:
The Tool Settings / MCU GCC Compiler / Include paths contains

Note that there are also Include Paths under other tools (eg, Assembler), and under C/C++ General.

Also check in other Configurations.

@cbcooper wrote:
How can I figure out where this warning is coming from?

I agree that Eclipse (on which CubeIDE is built) is unhelpful here.

@cbcooper wrote:
company policy is to build without warnings

Note that this is an IDE warning, not a compiler warning

PS:

As CubeIDE is Eclipse, a general search for "Eclipse Path Entry Problem" might help; eg,

https://stackoverflow.com/questions/18427492/how-to-remove-auto-discovered-paths-after-compiling-on-linux-from-eclipse-cdt-pr

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

cbcooper · ‎2026-03-12

As far as I can tell, the values in "Properties / C/C++ General / Paths and Symbols" are just a re-telling of the information I put in "C/C++ Build / Settings / Tool Settings / MCU GCC Compiler / Include paths".

I've checked both Release and Debug configurations.

The question you linked to on stackoverflow says to remove "$YOUR-PROJECT.sc" from "$WORKSPACE/.metadata/.plugins/org.eclipse.cdt.make.core" but for me that folder only contains specs.c and specs.cpp and they are both empty.

I do see there are lots of questions about Eclipse generating Path Entry Problems and I've tried several without success, they are all just workarounds anyway (delete files, close project, turn around three times, open project while closing left eye). I'm assuming it's some kind of interaction between Eclipse and STM32CubeIDE and that both parties are assuming it's the other one's fault.

Andrew Neil · ‎2026-03-12

@cbcooper wrote:
some kind of interaction between Eclipse and STM32CubeIDE and that both parties are assuming it's the other one's fault.

STM32CubeIDE is Eclipse.

Have you tried doing an Index rebuild?

(it's in the pop-up when you right-click the Project in the Project Explorer).

Otherwise I guess it's a case of deleting each Include Path entry until you find it ...

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Andrew Neil · ‎2026-03-19

@Andrew Neil wrote:
Note that there are also Include Paths under other tools (eg, Assembler), and under C/C++ General.

@cbcooper I've just had this very problem occur and it was, indeed, caused by entries in the Assembler Include Paths.

It seems that the paths had been added to both Compiler and Assembler at some point.

Have you checked that?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.