Closed andreaslundeen closed 2 weeks ago
Hi @andreaslundeen, this looks like an issue which was fixed in a65de0ab1f4f6b21b490ab3ba1c972bd82cd1a1b. In addition to that, there have been other fixes for reproducible builds as part of 0b376251dfa5d265a54800f002ef7d1c77e22787. These changes, along with the documentation have been first released in IDF v5.0. Since v4.4.x releases are EoL now, I can suggest either cherry-picking the fix commit into your local branch, or using espressif/idf Docker image to perform the builds.
FYI, currently there are a couple other open issues about builds not being reproducible in certain cases: https://github.com/espressif/esp-idf/issues/13680 (builds not reproducible if the toolchain directory is different: in progress, will be fixed soon) and https://github.com/espressif/esp-idf/issues/14267 (builds made on different OSes differ: might be fixed in a future toolchain release).
As already mentioned, fixes for most of these issues are available on master now, and the only outstanding known issue with reproducible builds can be tracker in https://github.com/espressif/esp-idf/issues/14267
Closing this one, if you think there is still something left unresolved then feel free to reopen.
Answers checklist.
IDF version.
v4.4.8
Operating System used.
Windows
How did you build your project?
Eclipse IDE
If you are using Windows, please specify command line type.
CMD
What is the expected behavior?
I expect to be able to reproduce exact same binary between different builds of same source code
What is the actual behavior?
The generated sections.ld looks different between the builds which causes the binaries to be different.
Steps to reproduce.
Building a project using 4.4.8 (and prev versions) from scratch where I build and link the IDF as a lib.
Build or installation Logs.
More Information.
No response