How did this work before? Was the user code supposed to set all these?
And, are we not using -Wundef (which would give a warning if undefined macros are used in #if statements)?
How did this work before? Was the user code supposed to set all these?
And, are we not using `-Wundef` (which would give a warning if undefined macros are used in `#if` statements)?
Yes, those were supposed to be set by the user.
The FSFW.h.in file is new and is able to set default values for undefined defines. This is how projects like FreeRTOS and LwIP sanitize the user configuration header file.
And as far as i know this warning is not used
Yes, those were supposed to be set by the user.
The `FSFW.h.in` file is new and is able to set default values for undefined defines. This is how projects like FreeRTOS and LwIP sanitize the user configuration header file.
And as far as i know this warning is not used
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
How did this work before? Was the user code supposed to set all these?
And, are we not using
-Wundef(which would give a warning if undefined macros are used in#ifstatements)?Yes, those were supposed to be set by the user.
The
FSFW.h.infile is new and is able to set default values for undefined defines. This is how projects like FreeRTOS and LwIP sanitize the user configuration header file.And as far as i know this warning is not used
Thanks for the clarification