On 7/3/2024 5:27 pm, Sebastian Huber wrote: > On 07.03.24 02:09, Chris Johns wrote: >> On 6/3/2024 8:33 am, Gedare Bloom wrote: >>> If script generation needs to be done, it should be implemented in >>> Python with input from the yml spec item as necessary to fill out a >>> templated script with variables to customize for the BSP, and with >>> appropriate injection of comments etc to allow traceability backward >>> to the original source data and source program that generated the >>> script. >> We cannot import the YML data in external code without coping it as it all >> resides in the wscript file. I would prefer seeing the YML python support >> moved >> into `spec` as modules with unitests that can be imported. This would allow >> us >> to add eco-system tools to support, manage and use the YML data. > > The module to work with specification items is here: > > https://github.com/RTEMS/rtems-central/blob/master/rtemsspec/items.py > > This stuff has tests, code formatting, static analysis, and even a CI script.
This does not help rtens.git ans that is the scope of this patch set. > Independent of this, working with the build specification items would be the > wrong approach. You need the input of a configured BSP. I do not understand what this means. What is the "input of a configured BSP"? Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
