Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

version #1

Open
Veix123 opened this issue Oct 6, 2020 · 1 comment
Open

version #1

Veix123 opened this issue Oct 6, 2020 · 1 comment
Assignees
@Veix123

Comments

@Veix123
Copy link
Collaborator

Veix123 commented Oct 6, 2020

  • hardcode version / git hash information into the firmware
    • are there any options for automating this?
  • respond with the version if the VERSION command is received over serial
@Veix123 Veix123 self-assigned this Oct 6, 2020
@Veix123
Copy link
Collaborator Author

Veix123 commented Nov 23, 2020

After having a discussion with @RValner, it seems that creating a separate version.h would be the best option. Compared to passing compile options, separated version.h results in much efficient compile process, since the whole mbed stuff doesn't need to be recompiled with each version change.
We will probably have a small script that increments the version fields and/or adds git hash to trace back the firmware to a specific commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Veix123 Veix123

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Veix123