Erik Rull <erik.rull@xxxxxxxxxxxxx> writes: > - The brute force way would be the checking of the .h-file > modification date (easily done via makefile). Is there a smart way of > handling real structure changes automatically? (E.g. if there is a > #define directive within the .h file and I change it, it would cause a > version increase, or worst case if I add a blank line somewhere it > would increase too) You could perhaps check whether the debugging information has changed. You can dump using, e.g., readelf --debug-dump. > - My code is checked into a CVS system. If there would be an > automatically changing of version numbers within the makefiles, each > person that retrieves the update also increases the version number > which could lead into more and more increasing numbers (x has compiled > and checked in V1, y checks out via update, compiles (version changes > also detected due to the differences in CVS) and increases to V2, if > then checked in, z checks out and increases again to V3 and so on). I > want to ensure that only the person that did the modifications > increases the version number once, but automatically. Can't help you there, sounds more like a process issue than a programming issue. Ian
