| Message ID | cover.1599826389.git.jan.kiszka@siemens.com |
|---|---|
| Headers | show |
| Series | 32-bit compat arch support | expand |
On 11.09.20 14:13, [ext] Jan Kiszka wrote: > This allows to build and install 32-bit packages for/on amd64 and arm64 > targets. SDK is enhanced as well. > > Changes in v2: > - switched from hello-isar to samefile as compat package, resolving > conflicts with 32-bit arch when building in parallel > - add doc entry > > Jan > > Jan Kiszka (4): > Add compat architecture support via multiarch > ci: Add compat arch support > doc: Enhance list of supported cross-archs, drop QEMU reference > doc: Describe new compat arch support > > doc/user_manual.md | 25 ++++++++++++++++--- > meta-isar/conf/local.conf.sample | 10 ++++++++ > .../recipes-app/samefile/samefile_2.14.bb | 6 +++++ > meta/classes/dpkg.bbclass | 8 +++--- > meta/conf/bitbake.conf | 3 ++- > meta/conf/distro/debian-common.conf | 3 +++ > .../isar-bootstrap/isar-bootstrap.inc | 14 ++++++++++- > .../buildchroot/buildchroot.inc | 5 ++++ > meta/recipes-devtools/sdkchroot/sdkchroot.bb | 1 + > scripts/ci_build.sh | 6 +++++ > 10 files changed, 72 insertions(+), 9 deletions(-) > Any feedback on this? We are about to move this into production, exposing it to end-users. Jan
On Mon, Sep 21, 2020 at 11:24:51AM +0200, Jan Kiszka wrote: > Any feedback on this? We are about to move this into production, exposing it > to end-users. Thanks for the info, will have a more detailed look and let you know. Regarding "qemuarm-stretch" stuff: Those reference verbatim file names under meta-isar/conf/multiconfig. Just cutting the "qemu" part is confusing as well, as the remaining part isn't how it's called in Debian. I've re-read the preceding paragraph, literally it doesn't imply only qemu stuff is cross-buildable; but I see what you mean. The obvious options are 1. to mention non-qemu configurations in the list and 2. rewrite the entries using Debian arch names ("stretch armhf", etc.). But let me ask the other way round, are there configurations in stock Isar that don't support cross-building? Do we need to document the ones that do so explicitly? With kind regards, Baurzhan.
On 21.09.20 11:41, Baurzhan Ismagulov wrote: > On Mon, Sep 21, 2020 at 11:24:51AM +0200, Jan Kiszka wrote: >> Any feedback on this? We are about to move this into production, exposing it >> to end-users. > > Thanks for the info, will have a more detailed look and let you know. > > Regarding "qemuarm-stretch" stuff: Those reference verbatim file names under > meta-isar/conf/multiconfig. Just cutting the "qemu" part is confusing as well, > as the remaining part isn't how it's called in Debian. > > I've re-read the preceding paragraph, literally it doesn't imply only qemu > stuff is cross-buildable; but I see what you mean. The obvious options are 1. > to mention non-qemu configurations in the list and 2. rewrite the entries using > Debian arch names ("stretch armhf", etc.). I would go for option 2. > > But let me ask the other way round, are there configurations in stock Isar that > don't support cross-building? Do we need to document the ones that do so > explicitly? Depends on what you define as being in stock Isar. If that implies having a multiconf in meta-isar and also just being experimental (riscv64), likely no. But there is also no statement that meta-isar defines what works with Isar, is there? Jan