Went to rebuild an image and updated the project from the old DS5 to a newer Arm Dev Studio (2022.2, this is the customer version so it's a hard requirement that can't be changed). We went from using the internal 16.1 armcc to the standalone 5.06u3 armcc since those are the certified versions required by the customer. The image files generated have different checksums despite using the same compiler. Investigating, the listing files show the same opcodes being generated which was confirmed by a diff of the object files, though there are some differences in the header and footer of the object files. In the master listing file (outfile.lst), files are being compiled/resolved in a different order. Under Arm Dev Studio, main.c is compiled first as it contains the first function encountered after the 'Start:' section, followed by the rest of the Resources. Under DS5, initialize.c and associated the config files went first (first physical files in the project) with main.c actually being the last thing compiled under DS5. It looks like that order difference is carried into the AXF file. Given the updates between the two, we also did change from calling the altera.elmap to using the intel_fpga.elmap.
So the question becomes, is there a way to force the old DS5 order of compilation/link in Arm Dev Studio?
Okay, so I just tried it with a relative file "--via=../makefile.armlink.exe.inputs" and it does NOT create or modify the file in that case. So the right answer is to wipe out the ${INPUTS} and make sure the argument for "--via" is outside the build configuration's directory. Thanks for the help!
The minor tweak from Stephen's prior answer:
1. Select project > Properties > C/C++ Build > Settings > Arm Linker
2. In Expert settings: Command line pattern, change${COMMAND} ${FLAGS} ${OUTPUT_FLAG} ${OUTPUT_PREFIX}${OUTPUT} ${INPUTS}to${COMMAND} ${FLAGS} ${OUTPUT_FLAG} ${OUTPUT_PREFIX}${OUTPUT}(i.e. remove " ${INPUTS}")3. Then select Arm Linker > Miscellaneous.Under Other flags, add--via=../makefile.armlink.exe.inputs