On 6/15/20 7:32 AM, Matthias Schiffer wrote:
I just think of ar71xx and ath79, where we have the same device but
different targets. Of course, the name won't be exactly equal, as ath79 will
have e.g. tplink_ prefix and ar71xx won't.
Isn't ar71xx removed from master builds? It's neither at snap
>>> I just think of ar71xx and ath79, where we have the same device but
>> different targets. Of course, the name won't be exactly equal, as ath79 will
>> have e.g. tplink_ prefix and ar71xx won't.
>> Isn't ar71xx removed from master builds? It's neither at snapshot
>> https://downloads.openwrt.o
> >> Sent: Sonntag, 14. Juni 2020 11:34
> >> To: openwrt-devel@lists.openwrt.org
> >> Subject: [OpenWrt-Devel] [PATCH][RFC] build: disable target name in
> >> image filename
> >>
> >> The target/subtarget information in image filenames is bare
: disable target name in image
filename
The target/subtarget information in image filenames is barely of any use for
developers or end users.
A developer reads the profile name and the target is either obvious due to
previous work or `cd targets/ && grep -r ` tells the target within
3m
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Paul Spooren
> Sent: Sonntag, 14. Juni 2020 11:34
> To: openwrt-devel@lists.openwrt.org
> Subject: [OpenWrt-Devel] [PATCH][RFC] build: disable target name i
On Sat, Jun 13, 2020 at 11:33:31PM -1000, Paul Spooren wrote:
> The target/subtarget information in image filenames is barely of any use
> for developers or end users.
>
> A developer reads the profile name and the target is either obvious due
> to previous work or `cd targets/ && grep -r ` tells
The target/subtarget information in image filenames is barely of any use
for developers or end users.
A developer reads the profile name and the target is either obvious due
to previous work or `cd targets/ && grep -r ` tells the target
within 3ms. If no buildroot is available `cat | tail -c 200`
