Open bryghtlabs-richard opened 1 month ago
Thanks for bringing up the issue, and sorry that we didn't explicitly mention the OS in the list of things that may still cause the builds to be non-reproducible. But yes, this specific issue was assumed to be part of "Versions of the build tools (CMake, Ninja) and the cross-compiler".
We can try to substitute these paths in a future toolchain release, however I'm afraid that we won't be creating a patch release of the toolchains used in v5.1.x.
No worries about a fix for v5.1.x, it's just the version I was using. Remapping those paths would be certainly be helpful, and may be the only thing left across different OSs with the same tool versions - I've only seen differences in those strings and differences in pointers that may have been offset due to those strings changing length.
Answers checklist.
IDF version.
v5.1.2
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
CMD
What is the expected behavior?
When building same application with same sources and same tool versions, output binaries should match, even if the build OS is different.
What is the actual behavior?
Some paths seem to be captured when building newlib, which will then be present in the application's .bin file.
Steps to reproduce.
idf.py build
Build or installation Logs.
No response
More Information.
I saw the documentation stated "Versions of the build tools (CMake, Ninja) and the cross-compiler" may cause differences, but this seems unrelated to that. Here is the first difference in HXD: