You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the sometimes-rapid-iteration, it would be useful to see a completely unique build number in the About box.
(In my projects, every build runs a script that increments version.h, so the about box or --help shows things like "build 4037".)
Can also include __DATE__ and __TIME__ to get a very unique number.
Ideally the build number is also on the file name, like FIRMWARE_5.6_4037.333 or whatever. (Right now I have two quick iterations in my downloads which are distinguished by an extra period in the filename :) )
The text was updated successfully, but these errors were encountered:
Which builds are those? I usually use numbers for significant changes…. And letters for minor fixes. I am pretty lazy about ensuring the about page gets upgraded consistently, mostly because the quick iterations, but typically ensure the file names are reflective.
@Frudah I think @distrakt is referring to an automatically generated number (by a script in the build process) that will be incrementing with every build. I have similar mechanisms in Platformio to maintain this number and generate a build version string from it. Once implemented you will not have to care about it any more.
Version
alpha6
What is the issue?
With the sometimes-rapid-iteration, it would be useful to see a completely unique build number in the About box.
(In my projects, every build runs a script that increments version.h, so the about box or --help shows things like "build 4037".)
Can also include
__DATE__
and__TIME__
to get a very unique number.Ideally the build number is also on the file name, like FIRMWARE_5.6_4037.333 or whatever. (Right now I have two quick iterations in my downloads which are distinguished by an extra period in the filename :) )
The text was updated successfully, but these errors were encountered: