Compile same source code of Mesh-SDK-2.2, got different hex file

RE: Compile same source code of Mesh-SDK-2.2, got different hex file

jowei — Fri, 14 Dec 2018 05:16:54 GMT

Hi tesc:

Thanks sharing the good knowledge of compiler,

After I set target option/compiler/supply absolute file path, then two folder's hex file are same, but I havn't check if this option will affect firmware behavior, thank you.

Joseph

RE: Compile same source code of Mesh-SDK-2.2, got different hex file

jowei — Fri, 14 Dec 2018 05:14:41 GMT

Hi awneil:

Yes, I mean Hex file, not ELF file

RE: Compile same source code of Mesh-SDK-2.2, got different hex file

awneil — Thu, 13 Dec 2018 17:39:04 GMT

jowei - You are talking about the actual Hex files - not the ELF ... ?

RE: Compile same source code of Mesh-SDK-2.2, got different hex file

tesc — Thu, 13 Dec 2018 17:08:54 GMT

Hi,

What compiler and toolchain are you using?

Reproducibility of software builds is an interesting topic. Some things to watch out for are the paths of the source files, timestamp of the build, random values generated at compile time, multithreaded build process leading to different placement of functions, data, etc. in the final binary, and more.

I do not have an overview of what factors change for our nRF5 SDK for mesh examples, and reproducibility is not a stated goal for our examples. It would however be interesting to see what is the difference between your hex files, just as awneil asked for. Then maybe we can provide some suggestions for what might cause that difference.

Regards,
Terje

RE: Compile same source code of Mesh-SDK-2.2, got different hex file

awneil — Thu, 13 Dec 2018 16:33:39 GMT

[quote userid="68472" url="~/f/nordic-q-a/41578/compile-same-source-code-of-mesh-sdk-2-2-got-different-hex-file"]I hope same source code can get same hex file[/quote]

Not necessarily.

How different, exactly, are the hex files?