Central | Remove configuration error when stack_checker_report is defined but the stack checker is not enabled. (#11)

[Gedare Bloom (@gedare)]

Gedare Bloom created an issue: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/issues/11



When `!defined(CONFIGURE_STACK_CHECKER_ENABLED) && defined(CONFIGURE_STACK_CHECKER_REPORTER)` there is `#error`. It was suggested this should not be an error.

https://gitlab.rtems.org/Hamzi/rtems/-/blob/main/cpukit/include/rtems/confdefs/extensions.h?ref_type=heads#L93

The following discussion from !4 should be addressed:

- [ ] @sebhub started a [discussion](https://gitlab.rtems.org/rtems/prequal/rtems-central/-/merge_requests/4#note_111290):  (+9 comments)

    > 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/-/issues/11
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/20260116/b579cc0d/attachment.htm>