1. Establish a place on our development network where a file will be kept.
In that file, is the build number we are currently working on.
2. Built a little C program to run on each build machine. The program opens
the network file, finds the version number, increments it and writes it back
to the network location.
3. Created a CEC file for versioning. This file, at PreMakeImg-time, runs
the program in 2 to increment the build number. You add this feature from
the catalog to platforms that need the versioning.
If you are going to try to write the version information into a resource or
something, you may need to move the increment step earlier in the build
process, before the driver, etc. is actually built. For us, the version
information is simply displayed on the screen when the user commands it, so
writing it to a text file is fine for us (the text file is included in the
nk.bin image).
Paul T.
Quote:> Is there an easy way to autoincrement version numbers for the OAL,
> bootloader, and/or drivers in CE 4.x?
1. Autoincrementing version numbers in MSVC 6??
Autoincrementing version numbers in MSVC 6?? So each build increments the
version number?
Can it be done with a standard MFC application?
Thanks
3. PRIMARY KEY and AUTOINCREMENT for a field in a .cdb?
5. media player version number
8. Windows Support Forums -- Sign-up and win a free t-shirt or free advertising.
9. Error: kernel-mode and user-mode drivers have different version numbers
11. wmp.dll version number problem
13. media player 7 version numbers