Examples | Configure against a coverage-enabled BSP fails (#2)

[Joel Sherrill (@joel)]

Joel Sherrill commented: https://gitlab.rtems.org/rtems/rtos/rtems-examples/-/issues/2#note_134917


I think there needs to be a distinction between building RTEMS with coverage enabled on itself and including the support for generating coverage. Likely ___gcov_merge_add _ and other support functions need to always be there but the magic compiler flags that enable coverage on RTEMS itself should be controlled by this flag.

@opticron do you think this might be that simple? Always build coverage support files but don't trip the coverage flags on unless this is specified?

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems-examples/-/issues/2#note_134917
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/20251013/ecadf5a0/attachment-0001.htm>