[elbe-devel] Debianize barebox

[Yegor Yefremov]

On Wed, Mar 18, 2020 at 3:08 PM Yegor Yefremov
<yegorslists at googlemail.com> wrote:
>
> On Tue, Mar 17, 2020 at 3:42 PM Yegor Yefremov
> <yegorslists at googlemail.com> wrote:
> >
> > How this process works?
> >
> > For am335x we need two steps/configurations: barebox-mlo.img and
> > barebox.img. Does it mean, one should create two folders: one for MLO
> > and the other for the bigger image and it results in two deb packages?
> >
> > Also there is a small bug either in the template or code:
> >
> > diff --git a/elbepack/debianize/panels/barebox.py
> > b/elbepack/debianize/panels/barebox.py
> > index 5a848b3f2..d53998600 100644
> > --- a/elbepack/debianize/panels/barebox.py
> > +++ b/elbepack/debianize/panels/barebox.py
> > @@ -31,7 +31,7 @@ class BareBox(Panel):
> >
> >          grid_elements = [
> >              {"imgname":imgname, "defconfig":defconfig},
> > -            {"cross":cross, "k_version":k_version}
> > +            {"cross_compile":cross, "k_version":k_version}
> >          ]
> >
> >          super(BareBox, self).__init__(grid_elements)
>
> I have more questions:
>
> 1. do we need to export KERNELRELEASE in
> elbepack/makofiles/debianize/barebox/rules.mako?
> Looks like barebox uses it to make u-boot think it is kernel during
> the development process.

KERNELRELEASE is working as intended.

> 2. what about barebox-tools package? Such scripts as
> bareboxcrc32-target and bareboxenv-target don't exist and bareboxcrc32
> and bareboxenv are compiled with the host compiler i.e. cannot be
> stripped and anyway of now use on target.

But this issue remains.

Yegor