Gedare Bloom commented on a discussion on spec/build/cpukit/librtemscpu.yml: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1071#note_148507 > cxxflags: > - ${COVERAGE_COMPILER_FLAGS} > enabled-by: true > -includes: [] > +includes: > +- contrib @opticron @amar any thoughts on how we should handle setting up include paths that point into contrib from cpukit? This also has the unfortunate side-effect of making the include path like `#include <ff.h>` which seems overly generic. It might be better to have something like `contrib/fatfs/fatfs` for the source import, and point to `contrib/fatfs` for the include root, so we have include path like `#include <fatfs/ff.h>`? -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1071#note_148507 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
