Full re-build always happens after debug session

[lpcware]

Content originally posted in LPCWare by ajones on Fri Nov 29 04:53:22 MST 2013
A project performs a full re-build after a debug session has been stopped and a fresh debug session is started although no files have changed. I am presuming that the project has been detected as changed but I haven't found out how to prevent this.

This causes problem when in debug/modify/debug mode as you change a single file and the whole project is re-built.

Steps to reproduce:

[list]
  [*]* Build project
  [*]* Debug project on target system
  [*]* Stop debugger
  [*]* Build project (all files are re-built)
  [*]
[/list]

How can I prevent the project from being marked as changed after a debug session?

[lpcware]

Content originally posted in LPCWare by ajones on Fri Nov 29 06:46:52 MST 2013
I had no problems performing a build after a build - it was associated with performing a debug.

I changed my includes to use standard directory slashes and the problem has been solved.

Thanks for the excellent and quick help.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Fri Nov 29 05:44:27 MST 2013
What happens if you build immediately after a build? i.e. is it anything to do with debugging, or is it something else?

I don't know whether this will help, but we had a similar report several year ago and this turned out to be because one of the files had

#include "..\file.h" /* notice use of Windows backslash */

And when it was changed to

#include "../file.h" /* use standard directory slash */

the problem went away.