Hi,
what is the actual benefit of this? The image building recipes are hard enough
to understand as-is, is it really worth it to replace a plain "kernel-bin |
append-dtb | lzma" command sequence with yet another variable indirection just
to safe a few bytes in the Makefile?
I could understand the
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Paul Oranje
> Sent: Sonntag, 2. Februar 2020 23:26
> To:
> Cc: openwrt-devel@lists.openwrt.org; Piotr Dymacz
> Subject: Re: [OpenWrt-Devel] [PATCH] ath79: i
Op 2 feb. 2020, om 18:20 heeft m...@adrianschmutzler.de het volgende geschreven:
> ...
> We could also use KERNEL_DTB_LZMA of course, but I do not think this will
> really bring a benefit.
Preferable, as it is more clear what it is supposed to do, e.g. to those that
are not enjoying the OpenWrt
Subject: Re: [OpenWrt-Devel] [PATCH] ath79: introduces KERNEL_LZMA
variable for common build sequence
Hi Adrian,
On 02.02.2020 13:48, Adrian Schmutzler wrote:
> This introduce a variable KERNEL_LZMA to replace the frequently used
> sequence "kernel-bin | append-dtb | lzma", similar t
CH] ath79: introduces KERNEL_LZMA
> variable for common build sequence
>
> Hi Adrian,
>
> On 02.02.2020 13:48, Adrian Schmutzler wrote:
> > This introduce a variable KERNEL_LZMA to replace the frequently used
> > sequence "kernel-bin | append-dtb | lzma", simila
Hi Adrian,
On 02.02.2020 13:48, Adrian Schmutzler wrote:
This introduce a variable KERNEL_LZMA to replace the frequently
used sequence "kernel-bin | append-dtb | lzma", similar to the
KERNEL_DTB variable in ramips target.
So in results we will have:
ramips: KERNEL_DTB = kernel-bin | append-
This introduce a variable KERNEL_LZMA to replace the frequently
used sequence "kernel-bin | append-dtb | lzma", similar to the
KERNEL_DTB variable in ramips target.
Signed-off-by: Adrian Schmutzler
---
target/linux/ath79/image/Makefile | 5 +++--
target/linux/ath79/image/common-mikrot