[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#45020] [PATCH 0/2] image: Add system field.
From: |
Mathieu Othacehe |
Subject: |
[bug#45020] [PATCH 0/2] image: Add system field. |
Date: |
Sat, 12 Dec 2020 09:30:54 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) |
Hey,
> I understand the need for an easier way to create images. However, I
> feel like <image> is the wrong place for ‘system’ and ‘target’: the
> image format, conceptually, has nothing to do with whether we’re
> cross-compiling, compiling for a specific system, etc.
On the one hand, I agree that adding "system" and "target" to <image>,
so that they can override the corresponding arguments doesn't feel
nice. On the other hand, I think that dealing with system/target is too
low level for most users.
When using Yocto, Buildroot or even OpenWrt, you say "build me an image
for that board/machine" and not, "build me an image for that board by
cross-compiling to this mysterious triplet".
If the user selects the image type "pine64" or "novena", it's obvious
that the image has to be built for ARM, so I think it makes sense to
hardcode it somewhere. The <image> record might not be the right
location for that information but I cannot think of another one.
Maybe someone else?
Thanks,
Mathieu
- [bug#45021] [PATCH 1/2] image: Add system field., (continued)
[bug#45022] [PATCH 2/2] image: Rename "raw" image-type to "efi-raw"., Mathieu Othacehe, 2020/12/03
[bug#45020] [PATCH 0/2] image: Add system field., zimoun, 2020/12/03
[bug#45020] [PATCH 0/2] image: Add system field., Efraim Flashner, 2020/12/09
[bug#45020] [PATCH 0/2] image: Add system field., Ludovic Courtès, 2020/12/11
[bug#45020] [PATCH 0/2] image: Add system field., Danny Milosavljevic, 2020/12/13