Without having a solution for your immediate problem - why not using a real version control system? Just install git or subversion, and off you go. No more copying stuff around, and no changes will get lost (and you even get a nice diff for each one...).
There is the function "Create Workspace Bundle" which ballows to generate a (compressed) archieve of your project. My experiences show that these archieves can be expanded anywhere and work as expected.
I presume you did a "Clean and Build Project" already.
Today it's building without errors. No changes were made to the project. I guess just chalk it up to quirky things that happen as software gets more and more complicated.
Responding to hli:
I'm using git after being frustrated with the "bundle" functionality many times. However there seems to be no clear direction on which files must be tracked (in addition to the obvious source and schematics) in order for correct build to be guaranteed. Do you know? I've been away from PSoC and this forum for a couple of months so apologies if this has been asnwered elsewhere...
Google found me a knowledgebase article about that:
Basically it boils down to this:
- all files / code that you wrote by yourself
- main.c and device.h
- *.cydwr, *.cyprj; *.cysch
- generated sources only when you added code to them (which is not recommended)
Anything else can be added to the ignore list of your SCCS.
If you are using PSoC3 and defines your own re-entrance function, you need the *.cyre file as well.