On Tue, Sep 22, 2020 at 08:49:20PM +0200, Heinrich Schuchardt wrote: > On 9/22/20 8:42 PM, Tom Rini wrote: > > On Tue, Sep 22, 2020 at 08:03:49PM +0200, Heinrich Schuchardt wrote: > > > >> Most users don't need the standalone API examples. Distributions like Suse > >> do not supply libgcc for cross-compiling and we cannot do without on ARMv8 > >> for building examples/. > >> > >> Make examples customizable via symbol CONFIG_EXAMPLES. It only defaults to > >> yes to ensure that we compile it on Gitlab CI. > > > > In this case we should not make it "default y" but instead enable it in > > some specific cases that go through CI. Probably once per arch/ > > directory on the QEMU / virtual target for that arch. > > default y if ARCH_QEMU would compile it
OK, lets do that in v2 please. > >> Cc: Matthias Brugger <mbrug...@suse.com> > >> Signed-off-by: Heinrich Schuchardt <xypron.g...@gmx.de> > >> --- > >> I wonder if we should not completely drop the standalone API. The UEFI API > >> has enough to run a standalone application. > > > > I'm certainly in favor of NOT adding support there for new > > architectures. I don't believe however we can drop it for existing > > architectures without some fairly large notice, and only then when UEFI > > is available as a reasonable replacement (ARM? Yes. MIPS? No idea). > > > > UEFI is low endian only. Right, so we can't just remove the standalone API but we can encourage new architectures to see if UEFI is right for them. -- Tom
signature.asc
Description: PGP signature