[RTEMS Project] #4123: rtems-bsps needs to be switched to look at waf info for BSPs

[RTEMS trac]

#4123: rtems-bsps needs to be switched to look at waf info for BSPs
---------------------------+---------------------
 Reporter:  Joel Sherrill  |       Owner:  (none)
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  6.1
Component:  tool           |     Version:  6
 Severity:  normal         |  Resolution:
 Keywords:  wafblocker     |  Blocked By:
 Blocking:                 |
---------------------------+---------------------

Comment (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.

--
Ticket URL: <http://devel.rtems.org/ticket/4123#comment:1>
RTEMS Project <http://www.rtems.org/>
RTEMS Project