My colleagues suggest this solution: use the BatchRunner PreLinker to touch a file before the IDE builds the rest of a build target.
In your build target's Settings window, choose BatchRunner PreLinker from the Pre-linker option. A new settings panel appears, BatchRunner Prelinker. In this panel, choose the batch file you'd like to run before each build. In this batch file, "touch" the source code file you want updated.
In a Windows batch file, you can "touch" a file like this:
type date.c > tmpdate.cdel date.cren tmpdate.c date.c
I hope this helps.
Thanks Marc, I'll give one (or both) of these a try.
Perhaps this could be a feature request for a future release of the IDE...force a build of selected files?
Hi Marc. I could be doing something wrong but it seems that the pre-linker batch runner isn't quite the right place to do this work.
If I touch the source file (I'm using a touch.exe in the batch file), it happens after the compile and leaves that source file 'dirty' as in always needing to be built (check mark in the left column of the files list in the project window). This could be considered ok, but isn't quite 'clean'.
If I delete the xxx.c.o file, the linker complains that it can't find the file in its NAMES list when it gets to the linking phase, which seems to make sense as I have just deleted the object file created by the compile process.
If I remember I can always just click in the left column of the files list and make that file dirty before a build...but automation is better than me remembering!
Message Edited by wre on 03-03-200601:54 PM
Retrieving data ...