Opened on 10/06/20 at 18:06:02
Closed on 11/05/20 at 20:16:18
#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: | ||
Blocking: |
Description
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
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: | new → closed |
In 4cd885c/rtems:
Note: See
TracTickets for help on using
tickets.
The
rtems-bsps
command needs to have some python code to read thespec
YAML files. This is currently in thewscript
along with the generated pickle data optimisation. I would like to have a common piece of python code in thespec
directoryrtems-bsps
andwscript
can share so the generated data can be shared.The
rtems-bsps
code needs to use the same pickled datawaf
uses. Without thisrtems-bsps
would suffer the same performance issueswaf
had early in it's development that lead to the generation solution. Invokingrtems-bsps
may result in the same regeneration messagewaf
produces but that is OK.A common python module for
wscript
andrtems-bsps
follows the model used in the spec data where something is defined once and reused. I believe there is code inrtems-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.