Chris Johns commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/582#note_127371 @gedare you are correct about with the right solution is to move the HAL to an external dependent library. Having the HAL in RTEMS is what I call the "corporate" approach where you can control all the factors in a release to make a "product". If we want to head down the path to remove HALs so users can build the version that suites I am fine with that but in the mean time I see this is a better process for handling HAL code we have in tree. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/582#note_127371 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
