Amar Takhar created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5299
Assignee: Amar Takhar ## Summary As part of the effort in https://gitlab.rtems.org/groups/rtems/-/epics/33 to move 3rd party code to `/contrib/` there needs to be a separation of building to isolate includes. Right now all 3rd party includes are usually moved to the general `/include/` directory. They all get installed in the same place which is fine but for building RTEMS we should ensure that only code that uses those headers has access to them. In general practice for some this may not be possible if a lot of RTEMS is using that library but for those that can we should. Some are already built in isolation such as `libz` so it's not a big deal to do this for everything else. Any RTEMS files that need access to those headers can be moved into that "library" in this case no libraries are built they are still objects so there is no extra steps this is a feature of waf that we should be leveraging. Development wise there is no change this is a build-system only change no RTEMS files (outside of `/contrib/` would move and no functional change would happen to the build system just how they are built and where the files site in the `/build/` directory. This also gives us a clear distinction of 3rd party usage within RTEMS as well as an added benefit which right now is impossible to tell unless you know what the headers are called and start grepping. Relates to https://gitlab.rtems.org/groups/rtems/-/epics/33 ## Steps to reproduce ### Pre-set options -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5299 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
