RTEMS | cpukit: Move FatFs core to cpukit/contrib (!1071)

[Gedare Bloom (@gedare)]

Gedare Bloom commented on a discussion on spec/build/cpukit/librtemscpu.yml: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1071#note_149418

 >  cxxflags:
 >  - ${COVERAGE_COMPILER_FLAGS}
 >  enabled-by: true
 > -includes: []
 > +includes:
 > +- contrib

I would handle this instead by moving `rtems-fatfs.h` to `cpukit/include/rtems/fatfs/` path and install it as part of the build, making it the public API for RTEMS applications using this fatfs. Then have the rtems-fatfs.h include "ff.h" and "diskio.h"  rewrite the `fatfs/rtems-*.c` files to include `<rtems/fatfs/rtems-fatfs.h>`, and set the install path for ff.h and diskio.h to be also `rtems/` so they get installed beneath the `rtems/` directory to avoid polluting the top-level include paths, and they will get picked up by `#include <rtems/rtems-fatfs.h>`. Although in theory that probably makes `#include <rtems/ff.h>` (and diskio.h) work, no one should ever really do that.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1071#note_149418
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/20260502/23a92666/attachment-0001.htm>