We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Ok, this can't be this hard! Please show me the error of my ways.
I am using Keil uVision, building for LPX40xx processors, and I want to crank the warning levels up (more strict). I'm used to using --pedantic with gcc and would like to be able to enable the same sort of syntax checking in my Keil project.
I see where I can add command line armcc options under "Misc Controls" within the "Options For Target / C/C+" tab, so based on this:
https://developer.arm.com/docs/100748/latest/using-common-compiler-options/controlling-diagnostic-messages
I've tried adding -Wpedantic, and I get: Fatal error: C3900U: Unrecognized option '-pedantic'.
I would also be fine with doing this on a file-by-file basis, by adding #pragma diag_warning statements to my source files, as hinted at here:
infocenter.arm.com/.../index.jsp
but I can't find a list of tags.
Any help would be gratefully appreciated.
Thanks Robert. --strict appears to not be the correct syntax. I tried this, and everything blows up, including the Keil-supplied files:
compiling I2C_LPC40xx.c..."no source": Error: command-line: #1055: language modes specified are incompatibleC:\Users\dtc46\AppData\Local\Arm\Packs\Keil\LPC4000_DFP\2.1.0\RTE_Driver\I2C_LPC40xx.c: 0 warnings, 1 error