-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
cmake: compute and display the reproducible checksum by default #51954
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -575,6 +575,7 @@ endif # BUILD_OUTPUT_UF2 | |
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @marc-hb This change is very useful! Thanks. Also for the incremental builds test, wouldn't make more sense to touch a header file like |
||
config BUILD_OUTPUT_STRIPPED | ||
bool "Build a stripped binary" | ||
default y | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. do not close a PR that are rejected and open a new PR with same changes, just hoping to get it approve a second time. Please keep this change in #51737 and let's continue the discussion there. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I explained why in #51737 why I closed it and I linked the two both ways - not hiding anything. In #51737 I made the mistake of stopping half-way, not checksumming the stripped binary. As a consequence all the (few) reviewers missed the point and focused on the wrong thing that I wrongly put in the PR title: the stripped file. The stripped file is a pure, low-level and mostly invisible implementation detail that does not matter. I don't care about the stripped file, it's only a means to an end. Finding reproducibility bugs like #48195 and all the others listed in #14593 is the only thing that matters. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As per other commit, rejecting as this is not something that should ever be enabled by default |
||
help | ||
Build a stripped binary zephyr/zephyr.strip in the build directory. | ||
The name of this file can be customized with CONFIG_KERNEL_BIN_NAME. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'm sure this is a very useful feature, just like printing of memory usage.
But still, printing of memory usage is user configurable, so why should sha256 checksum be always on ?
(I do note it's tied to strip)
zephyr/Kconfig.zephyr
Lines 462 to 463 in 261025a
Should this be a general option that users can enable, so that any output file,
bin
,hex,
s19
, etc can have this ?As a matter of fact,
bin
files are created per default, and a checksum on those would be more safe than using the elf file for checksumming.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree. "Strip" should not be synonymous with "compute & print checksum" and vice versa.