Hello everyone!
I've found myself in a spot of bother with Keil uVision 5.24.2.0 using ARM Compiler v5.06 update 5...although the build issues I have don't appear specific to these versions. Let me explain...
In my Keil project I have two targets: 'Release' and 'Debug'. The goal is to globally enable/disable various debug options and change formatted output simply by selecting the appropriate build target and compiling.
Here is how I tried to make it work:
- In 'Options for Target', C/C++ tab, 'Preprocessor Symbols' Define section, I have defined: 'DEBUG' for the Debug target 'noDEBUG' for the Release target all other settings are identical between the Debug and Release targets.
- I have a header file 'debug_config.h' in which I have enable/disable various debug options like so:
#ifndef __DEBUG_CONFIG_H #define __DEBUG_CONFIG_H #ifdef DEBUG #define DEBUG_BUILD 1 #else #define DEBUG_BUILD 0 #endif #if ( DEBUG_BUILD == 1 ) #define TEST_MODE_RECOGNIZER 1 #endif #endif
- In main.c and other source code files (which all #include "debug_config.h") I refer only to DEBUG_BUILD and TEST_MODE_* like this:
printf("IronMan Gen3.7 (%s)\r\n", (DEBUG_BUILD == 1) ? "Debug" : "Release"); #if ( TEST_MODE_RECOGNIZER == 1 ) printf("Jarvis 8.9b Test Mode\r\n"); #endif
With all that in place, if I 'Clean Targets', select 'Debug' target, then Build I will get the following output:
IronMan Gen3.7 (Debug) Jarvis 8.9b Test Mode
Perfect!
Now I switch to 'Release' target and without doing 'Clean Targets' I do Build. I find main.c is NOT compiled! Why not? Other files which don't #include "debug_config.h" and don't mention DEBUG, DEBUG_BUILD, or TEST_MODE_RECOGNIZER are compiled. Because main.c is not recompiled I get the same output as above! What I want of course is:
IronMan Gen3.7 (Release)
I understand that I did not change main.c source code, so from compiler perspective it thinks perhaps it doesn't need to retranslate it. However, I selected different Target, which had different Defines, so I expected that it would recompile main.c like it did with other files.
I note there is a 'Undefine' section in the Target C/C++ Preprocessor Symbols, but it is grayed out. I can't select or enter anything there, otherwise I would 'Undefine DEBUG' for the Release target.
So I am stumped...
I hope this provides clear example of what I would like to do. Obviously there's something I've done wrong or misunderstood...
Thanks for any advice or suggestions on this!
Best!
Thanks for the update!
1) Because if your decision mechanism... Okay, that makes sense! So if I do:
#if ( DEBUG_BUILD == 1 ) #define TEST_MODE_RECOGNIZER 1 #else #define TEST_MODE_RECOGNIZER 0 #endif
I pair it with conditional compilation test like this
#if ( TEST_MODE_RECOGNIZER == 1 ) ... #endif
Alternatively,
#define TEST_MODE_RECOGNIZER
paired with
#ifdef TEST_MODE_RECOGNIZER ... #endif
2) I think you misunderstood... Indeed! I had thought the order of the different Targets is what it meant, since it's possible to re-order them. Now it is clear why 'Undefine' preprocessor symbols is grayed out at the Target level! Can't undefine anything that hasn't been defined and a higher level...and Target level is at the top!
Thanks for picking up on that one! Silly me!
3) No. We were discussing options that you currently collect in a global header file... Ahh, thanks for the correction. I get it now. I should explore the Group hierarchy more. From your explanation I realize now I could better pair options to specific Groups; certainly options I introduce for my modules don't need to be applied to e.g. HAL modules provided by the the manufacturer.
4) You wouldn't. You would just put the second macro itself directly into the master Defines list instead. I see. That's easy enough for a few macros.
As-is, your conditional chaining of debug macros does not really gain you much anyway, compared to a bog standard, single DEBUG_BUILD macro that you just query directly. True. I had given an elementary example to illustrate my problem. In reality I have several levels of debug, starting with global DEBUG_BUILD under which there's TEST_MODE under which there's a list of individual TEST_*, each with several options to enable/disable individually. And that is just TEST_MODE.
With the conditional chaining of macros I find I can quickly and easily control the debug output. I like I can see in the code exactly what is enabled or disabled without having to Alt+F7 to get the 'Options for...' dialog.
But now that I understand how the Target/Group/File hierarchy works better, I will see if it can work well for me.
A wish to Keil... It would be super helpful if the Keil uVision IDE could track the current value of #define macros (& values) without compiling and then apply syntax highlighting/shading in the IDE code editor that reflects what would be compiled given the current state of Target/Group/File preprocessor symbol Defines/Undefines (in 'Options for...' dialog) and #defines in .h/.c files.