Central | Draft: acfg/if: Add configuration app option for stack-checker-reporter (!4)

[Sebastian Huber (@sebhub)]

Sebastian Huber started a new discussion on spec/acfg/if/stack-checker-reporter.yml: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/merge_requests/4#note_111290

 > +enabled-by: true
 > +index-entries:
 > +- stack checker reporter
 > +interface-type: appl-config-option
 > +links:
 > +- role: interface-placement
 > +  uid: domain
 > +- role: interface-ingroup
 > +  uid: group-stack-checker
 > +- role: constraint
 > +  uid: ../constraint/init-stack-checker-reporter
 > +name: CONFIGURE_STACK_CHECKER_REPORTER
 > +notes: |
 > +  This configuration option works in conjunction with 
 > +  ${stack-checker-enabled:/name}. If the stack checker is not enabled,
 > +  configuring stack reporter will result in a C preprocessor error.

Does this really have to be an error? Which bad things happen if you define this option and the stack checker is not enabled? I think it would be more convenient if you could just disable the stack checker and don't have to worry about additional stack checker customization options. During development you may want to run your application with or without the stack checker.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/merge_requests/4#note_111290
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20240819/f67d0289/attachment.htm>