-
-
Notifications
You must be signed in to change notification settings - Fork 19.3k
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.
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
Add user's BUILD: _date_ _time_ to M115 output #17957
Add user's BUILD: _date_ _time_ to M115 output #17957
Conversation
Is there a way to add the Build Directory path to this information? |
I could not find a macro that contains that but that does not have to mean anything. I actually found the __DATE__ variable kinda by accident. If you find a way to get the path at compile time it should be relatively easy to add. |
I don't mess with the makefile stuff very much. But almost for sure, the makefile knows where it is being invoked from. I wonder if we could pipe that information to a text file and some how package it up with the other M115 info? |
You can use platformio to set define. I have one that sets the git branch and build date this way. Add it to the platform extra scripts. Have it set the various extra defines, then in M115 have some ifdefs for the extra output maybe? |
Yes... That would be very helpful. I guess whether it helps a person or not depends on how they do their work. But I have a folder for each printer and copies of the entire build directory for various versions of that printer's firmware (with various configuration changes and new features under construction). So knowing the actual path to build tree that generated a printer's firmware is very useful when I come back to a printer that hasn't been modified (or maybe used) for a while. |
Co-authored-by: Scott Lahteine <[email protected]>
Co-authored-by: Scott Lahteine <[email protected]>
Co-authored-by: Scott Lahteine <[email protected]>
I added the buld-date and time to the end of the M115 report so I could determine if the firmware actually flashed (SD flash on the skr E3 mini can be flaky sometimes)
Benefits
Ability to tell when the running firmware was built and if a firmware flash succeeded, small quality of live improvement.