How does the Uv4.exe determine in what order source files are built? I have a project that I build on my local PC, and the same project being built on a build machine. The source files get compiled in a different order on the two machines, and the .hex file we end up with is different between the two machines. They are using the same version of uVision, compiling the same project files, and running the same command-line arguments.
We need to be able to reliably reproduce the .hex file generated on the build machine. I can build twice on my machine and get the same result, but what gets built on the build machine differs from my own. How can I force the project to be more consistent in how it builds the file?
No. It's not cross module optimisation that I enable. For the one I mean, you must specify a -feedback parameter (I think) in both the compile and link.
But since your rebuilding 3 times, I suspect it's not that.
What your describing is not something I see. Maybe someone else can suggest something.