RE: [PATCH v4 1/2] run imager in buildchroot-host on cross

["Moessbauer, Felix" <felix.moessbauer@siemens.com>]

> -----Original Message-----
> From: Anton Mikanovich <amikan@ilbers.de>
> Sent: Thursday, September 15, 2022 12:46 PM
> To: Moessbauer, Felix (T CED SES-DE) <felix.moessbauer@siemens.com>; isar-
> users@googlegroups.com
> Cc: Schild, Henning (T CED SES-DE) <henning.schild@siemens.com>; Schmidt,
> Adriaan (T CED SES-DE) <adriaan.schmidt@siemens.com>; ibr@ilbers.de; Kiszka,
> Jan (T CED) <jan.kiszka@siemens.com>
> Subject: Re: [PATCH v4 1/2] run imager in buildchroot-host on cross
> 
> 15.09.2022 12:35, Moessbauer, Felix wrote:
> > Hi,
> >
> > Interesting finding.
> > Are there any CI tests that catch this? At least I cannot find a CROSS test that
> builds the SDK.
> > Apart from that, Debian stretch is EOL since June 22.
> >
> > I'm fine with keeping the stretch targets, but then we could simply
> > disable CROSS by setting ISAR_CROSS_COMPILE_debian-stretch = "0" in the
> image.bbclass.
> >
> > If you could point me to a target for testing, I'm happy to add that.
> >
> > Best regards,
> > Felix
> >
> At least test_container_sdk test of our fast CI has do_populate_sdk target for
> stretch. And we still need stretch support for downstreams, so adding
> ISAR_CROSS_COMPILE override looks reasonable.

Ok, will do that. But then using ` ISAR_CROSS_COMPILE_amd64_debian-stretch = "0"`

One last question before implementing this:
Could it be that this is in fact just a badly written test?
While cross-building for distro-arch == host-arch is technically possible (and uses a different toolchain), it does not look like it provides a reasonable value.
Could it be, that we better simply add ` perform_build_test(...,cross=False)` to the ContainerSdkTest as this is done for all other tests?

Best regards,
Felix