Trying to use the uVision generated batch file to build the project. The batch file is generated fine, but running it produces an error for every call to armcc:
C:\ARM\LPC23xx_24xxSampleSoftware.r5\Keil\NewTest1>"C:\Keil\ARM\BIN31\ArmCC" --Via ".\obj\irq.__i" Fatal error: C3904U: Could not open via file '.\obj\irq.__i'.
There are no files in my project with '.__i' or '.__ia' extensions.
Considering previous speculations:
"They are, presumably, intermediate files that are - or should be - generated by earlier steps in the build?"
and:
"It looks like the 'real' (GUI) build generates a 'Via' file for each input file in the project, and then uses that to do the actual translation"
I tried the following experiment:
1. Open the uVision Project, and also open an Explorer window on your Objects folder - ensure both are visible simultaneously;
2. Start a build from the GUI;
3. Refresh the Explorer window while the build is running - you will see that files with those funny extensions are, indeed, created briefly while the build is in progress...
I see the intermediate files... As you say, the batch file build must not be calling the 'via file generator' module. No matter, I am pretty close to having real make files now. There are many differences in the output when I compare the uVision built .axf and the .axf built from my custom makefile. I have tried to match what was recorded in the .dep file, but it could be the link order is different so the binary image does not compare even though it is the same size.