output file compatibility for different OS versions

Asked by Errett Hogrefe

Besides the basic, well-known issues migrating files between a Windows and a Linux environment (e.g. line termination differences between DOS and UNIX text files), are there any other differences that can be expected for the various output files? I see from other answers that using the Windows version of the tools to compile to a specific target should produce the same binary that would result from compiling with the the Linux version of the tools with the same target/settings. Are there any known issues about migrating other output files (such as ASCII files used in Verilog $readmemh) from one OS to another? For example, performing the compile on Linux and migrating the output file(s) to Windows for integration into a simulation environment...?

Question information

Language:
English Edit question
Status:
Solved
For:
GNU Arm Embedded Toolchain Edit question
Assignee:
No assignee Edit question
Solved by:
Terry Guo
Solved:
Last query:
Last reply:
Revision history for this message
Best Terry Guo (terry.guo) said :
#1

I can confirm that tool chain with same version will produce same ELF files no matter the build machine is Linux, Windows or Mac OS. If the produced ELF files are different (except things like time stamp), then it should be a bug of tool chain, please report this if you have. There is one question about this topic, it turns out user was using different tool chain.

So for your last question, I think you can do so.

Revision history for this message
Errett Hogrefe (ehogrefe) said :
#2

Thanks Terry Guo, that solved my question.