Already known issue: we know that changing the project structure (I mean renaming folders & projects) is painful because of the necessary manual operations to update the include settings.
We’ve raised a bug on Eclipse side to ask them working on the topic (bugs.eclipse.org/bugs/show_bug.cgi?id=313495), as this kind of refactoring is perfectly managed in the Java IDE, but not in the C/C++ one.
Meanwhile, we’ll try to implement workarounds.
One tip we’ll probably implement: in your project settings, use the ${PrjName} variable instead of the hard-coded project name for your include settings: they will be automatically updated when the project is renamed.
(By the way, renaming the project in Eclipse automatically renames the folder on the disk.)
You’re probably right; as soon as you don’t use the default location for the project, Eclipse won’t rename the folder (since it is “out of the workspace control”). The initial folder you’ve initially chosen may be also not named like the project within Eclipse…