linked resource not found for #include

[PerennialNovice]

Hi,
I use 4.4.2 on windows

We have multiple projects that use some common files that are linked to out of the corresponding projects. Common files are just a folder, no cdt/sloeber/eclipse project. However all three projects are grouped under one empty root project. (Don't know if this is relevant so I guess I better mention it)
Now, to add confusion, we changed HW in the development process and now have to support two different targets/board types.
To do so, I created a separate new project and just link to the existing code. So in this project folder there exist only eclipse and sloeber config files, and the build files.

For a reason we needed to include a project-specific file in the common codebase. Which works fine within the original setup by only adding the corresponding project path to the included folders list in project -> properties ->C/C++ build -> Settings

But it does not work within the project that only links to the source code. I get a "fatal error - file or directory not found" here, which I dont understand why this happens ...

To add to my confusion, selecting the corresponding filename in the include statement and hitting F3 brings me to the correct file :/

[jantje]

First off
What I see here is plain eclipse cdt usage and not really related to sloeber functionality.

But it does not work within the project that only links to the source code. I get a "fatal error - file or directory not found" here, which I dont understand why this happens ...

I assume this is a result from the build

To add to my confusion, selecting the corresponding filename in the include statement and hitting F3 brings me to the correct file :/

This is a result from the code analyzer/indexer.
So basically you see a difference in the 2 build systems.

As the build fails you should look at what the failing build command looks like and try to find out why the file is not found.

[PerennialNovice]

Thanks for the clarification!
I currently ran in some other problems so cannot investigate this
I assume I have a command-line length problem too :/
[edit] this happens only with make -clean and it is the rm command, I think
28.998 chars is fine
33.295 chars give me an error 87 - which could indicate a problem with the length according to some quickly googled comments

[jantje]

this happens only with make -clean and it is the rm command,

In new Sloeber clean will be delete the build folder. (Don't hold your breath)

[PerennialNovice]

new Sloeber?

Now that's exciting news!
Any guess on the release date so far?

[jantje]

Been working on it for over a year now.
I'm rewriting managed build (that is the CDT part Sloeber is build on) to be able to fix some long lasting issues in regards with archiving libraries before linking.
Lets hope this year (2024) we'll have a release.

[jantje]

Any progress on this?

[PerennialNovice]

Nope...

the initial error went away after I recreated all projects and includes etc.
So this must have been some incorrect linking somewhere

the error 87 / command line length problem persists, though.
Inspired by your answer, I just delete the Release-folder when I want to do a complete build from scratch

[jantje]

That makes this issue in my book a "one of" and a duplicate.

[PerennialNovice]

yeah, can be closed and you can forget about it and move on to other fun things :)