RTEMS Source Builder | Discussion: Integrating safeclib headers with Newlib (#201)

[YASH BHIWANIA (@Yash)]

Issue created by YASH BHIWANIA: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/work_items/201



With the initial per-BSP RSB recipe for `safeclib` wrapping up in !287 , Joel mentioned we should start figuring out the next step: header integration.

To recap the goal: we need to expose the C11 Annex K prototypes (like those in `<string.h>` and `<stdlib.h>`) to RTEMS users. These need to be properly guarded by the `__STDC_LIB_EXT1__` macro, which is defined in `sys/features.h`.

Since the plan is to keep `safeclib` as an RSB add-on rather than merging it directly into the Newlib tree, I'm trying to figure out the best plumbing for this.

A couple of ideas:

* Do we have the RSB patch the standard Newlib headers post-install so they `#include` the `safeclib` headers?
* Or should we just overlay the `safeclib` headers directly into the toolchain's include directory?

@joel  @rurban @wmthornton-dev  — I'd love to get your thoughts on the cleanest way to wire this up before I start writing the multilib and integration code.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/work_items/201
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-0sioxph7srouak1fxhycg6faq-e/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help


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