Christian Mauderer started a new discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1548#note_161542 It seems that the configuration of the BSP is a bit more complex than it has to be. Why don't you just remove the `ESPRESSIF_CHIP_VARIANT` in the `bspesp32c3db.yml` and replace it with a fixed `c3`? It's a BSP that explicitly targets the c3. So the `ESPRESSIF_CHIP_VARIANT` will always be `c3` in that file. I don't see an advantage of a configurable string at that point. Also note that the include is already configurable in `spec/build/bsps/riscv/esp32/optvariant.yml`? So if someone creates a bspesp32x7xx.yml in the future, it's no problem if that BSP uses a fixed `x7` in its destination path. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1548#note_161542 You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/namespace/49/sent_notifications/6-6nsud52zvzy7dxi7p5dxj9tpa-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
