#4123 closed enhancement (fixed)

rtems-bsps needs to be switched to look at waf info for BSPs

Reported by: Joel Sherrill Owned by: Sebastian Huber <sebastian.huber@…>
Priority: normal Milestone: 6.1
Component: tool Version: 6
Severity: normal Keywords: wafblocker
Cc: Blocked By:


rtems-bsps depends on autoconf. It must be fixed to depend on waf BSP configuration information before we can switch from autoconf.

Change History (2)

comment:1 Changed on 10/07/20 at 00:19:24 by Chris Johns

The rtems-bsps command needs to have some python code to read the spec YAML files. This is currently in the wscript along with the generated pickle data optimisation. I would like to have a common piece of python code in the spec directory rtems-bsps and wscript can share so the generated data can be shared.

The rtems-bsps code needs to use the same pickled data waf uses. Without this rtems-bsps would suffer the same performance issues waf had early in it's development that lead to the generation solution. Invoking rtems-bsps may result in the same regeneration message waf produces but that is OK.

A common python module for wscript and rtems-bsps follows the model used in the spec data where something is defined once and reused. I believe there is code in rtems-central that could be exported (copied into rtems.git) and used but I have not looked into this. The exporting could be handled in a similar way to the generation procedures in place for documentation and headers.

comment:2 Changed on 11/05/20 at 20:16:18 by Sebastian Huber <sebastian.huber@…>

Owner: set to Sebastian Huber <sebastian.huber@…>
Resolution: fixed
Status: newclosed

In 4cd885c/rtems:

rtems-bsps: Use build specification items

Close #4123.

Note: See TracTickets for help on using tickets.