I'm in the process of migrating a project from CCS3.3 to CCS4.2 and I'm stymied with the right way to define pre-build steps.
In CCS3.3, I could do something like this
.\create.bat
as a pre-build step on the Build Options dialog box and it would run at every build to create a .h file for me that would then get compiled into my code. Because of the relative path, anyone could use the batch file; we would commit it into Subversion at the top level of our project tree and everyone was happy. CCS would find the file and run it before building anything.
The purpose of the script was to create a timestamp that would get built into the binary, which we could then query at runtime, so we knew when the binary was actually built.
I'm not able to do this in CCS4, when I try to build I get "The system cannot find the file specified." apparently from a call to CreateProcess().
How do I specify an external pre-build command with a relative path that will execute on every build. Is there any reference to how CCS4 is executing these commands?
Thanks! Erik