[PATCH 4/6] build: Add support to make bootloader images

[Gedare Bloom]

On Mon, Mar 4, 2024 at 12:19 AM Chris Johns <chrisj at rtems.org> wrote:
>
>
>
> On 1/3/2024 9:57 pm, Sebastian Huber wrote:
> > On 29.02.24 00:05, Chris Johns wrote:
> >>>> If it is will the details be exported in the pkgconfig file and made available
> >>>> for users building applications in a consistent and easy to use way?
> >>> Application build systems can query the tool using the RTEMS_MKIMAGE package
> >>> configuration varible, for example:
> >>>
> >>>    pkg-config --variable=RTEMS_MKIMAGE
> >>> ${prefix}/lib/pkgconfig/${ARCH}-${BSP_NAME}.pc
> >> Nice. This is my preferred way of handling this.
> >>
> >>> If the BSP does not provide a tool, then the variable RTEMS_MKIMAGE is set to
> >>> "false".
> >> So the process has to be a single command?
> >
> > Yes, a single command which is written in Python. For the U-Boot image it
> > converts the ELF file to binary, then to a gz file, then to the U-Boot image.
>
> I see it is in a YAML spec file. Sorry that is a no from me. See below.
>
+1

We should not be in the habit of serializing source code inside a data
file without very good reasons to do so. This feels wrong.

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.