NetBurner Community Forum

I notice that many of the NB source files have a revision number, something like:
/* $Revision: 1.41 $ */


Is there an automated way to update a version number like this for all the files in a project each time they are built? Tod had a link about this a while ago, but I could not quite get it wired into the build options. That method seemed to just update a special line, one including the format:
AssemblyVersion("1.0.1.1")

Also, even if I could add that to the CDT C/C++ Build Section (which I didn't figure out), it seems like it would be great to define a way to do this for all new projects. Any idea if there is a way to automate that along with other things like the inclusion of specific libraries into a standard "newProject" template?

Tod's link is:
http://syncor.blogspot.com/2008/06/bett ... embly.html

thanks!

That version you see on our source is updated automatically by CVS. I suppose if you used some source control on your project files, you could make it work that way. I do not know if its possible to just create automatically incrementing versions on source with NBEclipse alone.

What you are referring to appears to be a source revision control number that can be added and updated via the build system to each file. I never really saw the point of this unless you distribute source code outside of a SCM system (like NB does). For everyone else it just strikes me as clutter that a maintenance programmer has to wade through or an extremely poor substitute for an SCM system.

My blog post was really about updating one part of one file automatically via a custom program to create a build number (it was geared towards Visual Studio and only worked so so for Eclipse). I now prefer to just use a build number based on the revision number from my svn repository.

I just posted the steps on how to do this for anyone using TortoiseSvn and Eclipse. It's considerably easier than the previous approach. I like having the revision number available for my ID? command so for any instrument I have out there I can always extract that code from the SCM to rebuild it if necessary. I also usually spit out this number via the debug serial port when the instrument boots.

Tod