RE: [avr-gcc-list] Adding date/version information to project??

[Matt.VanDeWerken]

That's fantastic Dave, thanks for the suggestion; I was going to make
the buildnumber like you have suggested, but couldn't think of a good
reason for the extra complication. Your suggestion has intrigued me to
try it (tomorrow - it's hometime right now).

I wonder if it can be a part of the script itself, and then have the
script edit itself in place (using sed -i)?? Hrm, something to try...

If this works, it's much better than what I originally had because the
fluff is mucho reduced (one less arbitrary file in the build directory).

Cheers,
Matthew van de Werken - Electronics Engineer
CSIRO E&M - Rock Mass Characterisation - 1 Technology Court - Pullenvale
- 4069
p: (07) 3327 4142 * f: (07) 3327 4455 * e: address@hidden
"We do not inherit the earth from our ancestors, we borrow it from our
children." 
-- Native American Proverb

> -----Original Message-----
> From: Dave Hylands [mailto:address@hidden 
> Sent: Wednesday, 30 November 2005 5:37 PM
> To: Van De Werken, Matt (E&M, QCAT)
> Cc: address@hidden
> Subject: Re: [avr-gcc-list] Adding date/version information 
> to project??
> 
> 
> Hi Matt,
> 
> > Having solved all that, I wanted to add an auto-incrementing build 
> > number to the build process, which lives in program memory. 
> Here's how 
> > I did it:
> 
> One slight enancement to consider. If you make the file which 
> contains the build number look like this:
> 
> =====8><--------------------------------------------------------------
> # This is the current build number of the latest build
> # DO NOT EDIT THIS FILE - it is updated automagically
> # by the build process.
> 
> BUILDNUMBER=6
> =====8><--------------------------------------------------------------
> 
> Then the file can be included by make (in case you want to 
> include the build number in part of a generated filename) or 
> similarly it can be sourced by a shell script.
> 
> --
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>