Threaded Mode | Linear Mode

ijabbott · (This post was last modified: 05-01-2018 04:27 PM by ijabbott.)

(04-30-2018 05:32 PM)burkhard Wrote: I think you can always grab "the latest" build via https://sourceforge.net/p/wp34s/code/HEA...realbuild/
At least, that's what I always do.

Ooh! I didn't realize the built binaries were included in the source code repository. In general, they usually just contain the (source) files used to build the binaries.

Quote:Based on this, the latest build is 3.3901 dating from 25 Mar 18.
I updated mine to that level from a couple of versions earlier (3887 I think).
(I believe I used flashing file calc_xtal_full.bin since I have the crystal installed)
Following the update from 3887→3901, the command VERS returns 3899 instead of the 3901.
So it looks to me like when they went from 3899→3901, they may have forgotten to update the version tag on at least the calc_xtal_full.bin file I used. I couldn't have grabbed the wrong file, because only the current ones are on that page. Possibly, though, they forgot to update one (or more) of them to really be at 3901 and left the older version instead (in which case I am truly running 3889). Anyhow, has anyone else tried to flash 3901 and have flashing go well, but VERS = 3889 reported? Thanks!

The number displayed by VERS seems to be the latest SVN revision number at the time of the build plus 1. The act of committing the built binaries back into the repository will bump the SVN number by 1, so presumably the +1 is to compensate for that. The only reason I can think of for some of the binaries displaying the wrong revision in the VERS command is that perhaps not all the binaries committed to SVN are the result of a "clean" build state.