Compiling your Kiel µVision projects from the commandline should be easy, and out of the box it is resonable simple. However the Commandline interface is very limited and it has basically not changed since 2011.
The KeiluVisionBuilder.cmd batch script attempts to handle the following situations:
- Suppress tge compiler Windows GUI for error reporting; which is especially a probelem when using the compiler on a build server.
- Operates on all the output streams from the compiler; Strangely the Keil uVision compiler creates up to two sets of output: Either none, one, the other or both output files are created.
- When the Flex license server is used, a number of conflicts can occour, so in this script you can:
- Define a number of times you want to retry a build
- Set the interval between attempted builds.
- Successfully recover if the license is suddenly withdrawn during a build.
Originally published in this Stack Overflow answer.
Dear author, I come across your script while searching for method to build Keil uVision 5 project automatically from build pipeline. May I ask how the action of "Checking-out Flexnet license before build, checking-in afterwards" is handled in the script? There seems to be no explicit statement for license actions. The way in which the script is currently written seems to suggest that, the license is automatically booked/checked-out when the uVision executable is invoked from the command line. Is this the case? Your kind confirmation would be highly appreciated!