From: Alexander Smirnov <asmirnov@ilbers.de>
To: isar-users@googlegroups.com
Cc: Alexander Smirnov <asmirnov@ilbers.de>
Subject: [PATCH v3 0/7] Isar cross-compilation support
Date: Tue, 17 Jul 2018 16:18:04 +0300 [thread overview]
Message-ID: <20180717131811.14239-1-asmirnov@ilbers.de> (raw)
Hi everybody,
sorry for the delay, this is the third version of cross-compilation
support for Isar.
Supported targets for cross-compilation:
- stretch armhf
- stretch amd64
Artifacts could be cross-compiled:
- dpkg.bbclass users
- dpkg-raw.bbclass users
- kernel
Known issues:
- if target and host architectures are the same, there is no need
to use host buildchroot.
- kernel module doesn't support cross-compilation. Default linux-headers
package depends from target gcc binaries. So attempt to install, for
example linux-headers-armmp, tries to install gcc:armhf, what rises
conflict with the host tools.
To enable cross-compilation, the variable ISAR_CROSS_COMPILE should be set
to "1" in local.conf file.
With best regards,
Alex
Alexander Smirnov (7):
isar-bootstrap: Update routine to determine host arch
buildchroot: Split generic part
buildchroot: Add host buildchroot
isar-bootstrap-helper: Add target architecture for dpkg
build.sh: Add additional parameter
cross-compilation: Introduce variable switch
linux: Add cross-compilation support
meta-isar/conf/local.conf.sample | 5 ++
meta/classes/dpkg-base.bbclass | 19 ++++-
meta/classes/dpkg.bbclass | 4 +-
meta/classes/isar-bootstrap-helper.bbclass | 13 +++-
meta/classes/wic-img.bbclass | 3 +-
meta/conf/isar-bitbake.conf | 3 +-
.../buildchroot/buildchroot-host.bb | 31 ++++++++
.../buildchroot/buildchroot-target.bb | 54 ++++++++++++++
meta/recipes-devtools/buildchroot/buildchroot.bb | 83 ----------------------
meta/recipes-devtools/buildchroot/buildchroot.inc | 37 ++++++++++
meta/recipes-devtools/buildchroot/files/build.sh | 17 ++++-
meta/recipes-kernel/linux-module/module.inc | 7 ++
meta/recipes-kernel/linux/files/build-kernel.sh | 16 +++++
meta/recipes-kernel/linux/linux-custom.inc | 4 +-
14 files changed, 200 insertions(+), 96 deletions(-)
create mode 100644 meta/recipes-devtools/buildchroot/buildchroot-host.bb
create mode 100644 meta/recipes-devtools/buildchroot/buildchroot-target.bb
delete mode 100644 meta/recipes-devtools/buildchroot/buildchroot.bb
create mode 100644 meta/recipes-devtools/buildchroot/buildchroot.inc
--
2.1.4
next reply other threads:[~2018-07-17 13:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 13:18 Alexander Smirnov [this message]
2018-07-17 13:18 ` [PATCH v3 1/7] isar-bootstrap: Update routine to determine host arch Alexander Smirnov
2018-07-17 13:18 ` [PATCH v3 2/7] buildchroot: Split generic part Alexander Smirnov
2018-07-17 13:18 ` [PATCH v3 3/7] buildchroot: Add host buildchroot Alexander Smirnov
2018-07-17 19:48 ` Jan Kiszka
2018-07-17 13:18 ` [PATCH v3 4/7] isar-bootstrap-helper: Add target architecture for dpkg Alexander Smirnov
2018-07-17 13:18 ` [PATCH v3 5/7] build.sh: Add additional parameter Alexander Smirnov
2018-07-17 13:18 ` [PATCH v3 6/7] cross-compilation: Introduce variable switch Alexander Smirnov
2018-07-17 13:18 ` [PATCH v3 7/7] linux: Add cross-compilation support Alexander Smirnov
2018-07-17 13:38 ` [PATCH v3 0/7] Isar " Jan Kiszka
2018-07-17 14:40 ` Jan Kiszka
2018-07-17 15:06 ` Alexander Smirnov
2018-07-17 15:18 ` Alexander Smirnov
2018-07-17 15:24 ` Jan Kiszka
2018-07-17 15:29 ` Alexander Smirnov
2018-07-17 15:41 ` Alexander Smirnov
2018-07-17 19:45 ` Jan Kiszka
2018-07-17 20:48 ` Alexander Smirnov
2018-07-18 7:06 ` Jan Kiszka
2018-07-18 8:19 ` Jan Kiszka
2018-07-18 8:37 ` Jan Kiszka
2018-07-18 18:52 ` Alexander Smirnov
2018-07-18 19:00 ` Jan Kiszka
2018-07-19 20:59 ` Alexander Smirnov
2018-07-20 5:56 ` Jan Kiszka
2018-07-22 20:15 ` Alexander Smirnov
2018-07-22 20:32 ` Alexander Smirnov
2018-07-22 21:54 ` Jan Kiszka
2018-07-23 6:55 ` Jan Kiszka
2018-07-24 8:21 ` Jan Kiszka
2018-07-22 21:40 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180717131811.14239-1-asmirnov@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox