From: Henning Schild <henning.schild@siemens.com>
To: Claudius Heine <ch@denx.de>
Cc: Alexander Smirnov <asmirnov@ilbers.de>, <isar-users@googlegroups.com>
Subject: Re: [RFC] [PATCH 0/9] Initial cross-compilation support
Date: Thu, 14 Jun 2018 14:24:18 +0200 [thread overview]
Message-ID: <20180614142418.6e490d83@md1pvb1c.ad001.siemens.net> (raw)
In-Reply-To: <1b45959cb29031b6d45d3243c2449656cb9380e0.camel@denx.de>
Am Thu, 14 Jun 2018 14:04:47 +0200
schrieb Claudius Heine <ch@denx.de>:
> Hi,
>
> On Wed, 2018-06-13 at 15:07 +0200, Alexander Smirnov wrote:
> > Hi all,
> >
> > this series introduces basic cross-compilation support for Isar. The
> > implementation
> > is based around new entity - buildchroot-cross, which is quite
> > similar to original
> > buildchroot, but has host architecture.
>
> Here is a crazy idea from me and Henning:
> Have you tried just installing an amd64-arm cross toolchain into the
> existing arm buildchroot, then switch to it from the 'native'
> toolchain using a combination of PATH variable entries, symlinks
> and/or wrapper scripts and let binfmt deal with calling the amd64
> binaries of the toolchain in the arm chroot environment?
Another idea that comes very close to the SDK series. How about the
cross_build_chroot contains just the compiler and whatever the compiler
needs. Then we mount buildchroot/rootfs into cross_build_chroot/sysroot
and smuggle in the "--sysroot /sysroot/" i.e. by putting wrapper
scripts for gcc and friends into /usr/local/bin/.
Similar approach, but we do not risk breaking the buildchroot by
forcing an alien compiler into it. And we use less binfmt magic ...
Both the cross-compile and the SDK are very similar and if cross builds
on top of SDK we should be on the right track.
Henning
> This way the arm system would think that you are compiling nativly
> while in fact you are using a cross compiler that is not emulated.
>
> Would that work?
>
> Cheers,
> Claudius
>
> >
> > This series tested for the following configuration only:
> >
> > $ bitbake multiconfig:qemui386
> >
> > In this build:
> > - libhello is cross-compiled
> > - example-hello is compiled traditionally (but it's successfully
> > linked with libhello)
> >
> > TODO list:
> > - Depending on the target architecture, various host tools should
> > be installed. For example
> > binutils package has the following names:
> > * binutils
> > * binutils-x86-64-linux-gnu
> > * binutils-arm-linux-gnueabihf
> > - Cross-dependency installation. This topic is still open for me
> > because 'mk-build-deps' tool
> > doesn't work here correctly. For example package depends on
> > binutils, but instead of
> > installation of 'binutils-arm-linux-gnueabihf' it tries to
> > install 'binutils:armhf' and ruins
> > the rootfs.
> >
> > So, as usually, comments and suggestions are welcome :-)
> >
> > With best redgards,
> > Alex
> >
> > Alexander Smirnov (9):
> > isar-bootstrap: Add routin to determine host arch
> > isar-bootstrap: Move common part to include
> > isar-bootstrap: Add host architecture support
> > isar-bootstrap-helper: Add parameter to set arch
> > buildchroot-cross: Initial implementation
> > classes/dpkg*: Relocate dependency from buildchroot
> > classes/dpkg*: Drop hardcoded buildchroot blobs
> > classes/dpkg-cross: Initial implementation
> > [FOR TESTING] libhello: Switch to cross compilation
> >
> > meta-isar/recipes-app/libhello/libhello.bb | 2 +-
> > meta/classes/dpkg-base.bbclass | 17 +-
> > meta/classes/dpkg-cross.bbclass | 15 ++
> > meta/classes/dpkg-raw.bbclass | 7 +-
> > meta/classes/dpkg.bbclass | 7 +-
> > meta/classes/image.bbclass | 2 +-
> > meta/classes/isar-bootstrap-helper.bbclass | 13 +-
> > meta/conf/isar-bitbake.conf | 1 +
> > .../isar-bootstrap/isar-bootstrap-host.bb | 44 ++++
> > .../isar-bootstrap/isar-bootstrap-target.bb | 44 ++++
> > meta/recipes-core/isar-bootstrap/isar-bootstrap.bb | 259 ---------
> > ------------
> > .../recipes-core/isar-bootstrap/isar-bootstrap.inc | 223
> > ++++++++++++++++++
> > .../buildchroot/buildchroot-cross.bb | 53 +++++
> > meta/recipes-devtools/buildchroot/buildchroot.bb | 2 +-
> > .../buildchroot/files/build-cross.sh | 29 +++
> > 15 files changed, 443 insertions(+), 275 deletions(-)
> > create mode 100644 meta/classes/dpkg-cross.bbclass
> > create mode 100644 meta/recipes-core/isar-bootstrap/isar-bootstrap-
> > host.bb
> > create mode 100644 meta/recipes-core/isar-bootstrap/isar-bootstrap-
> > target.bb
> > delete mode 100644 meta/recipes-core/isar-bootstrap/isar-
> > bootstrap.bb
> > create mode 100644 meta/recipes-core/isar-bootstrap/isar-
> > bootstrap.inc
> > create mode 100644 meta/recipes-devtools/buildchroot/buildchroot-
> > cross.bb
> > create mode 100644 meta/recipes-devtools/buildchroot/files/build-
> > cross.sh
> >
> > --
> > 2.1.4
> >
next prev parent reply other threads:[~2018-06-14 12:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 13:07 Alexander Smirnov
2018-06-13 13:07 ` [PATCH 1/9] isar-bootstrap: Add routin to determine host arch Alexander Smirnov
2018-06-14 11:23 ` Henning Schild
2018-06-15 11:11 ` Alexander Smirnov
2018-06-15 11:15 ` Jan Kiszka
2018-06-13 13:08 ` [PATCH 2/9] isar-bootstrap: Move common part to include Alexander Smirnov
2018-06-13 13:08 ` [PATCH 3/9] isar-bootstrap: Add host architecture support Alexander Smirnov
2018-06-14 11:27 ` Henning Schild
2018-06-15 11:09 ` Alexander Smirnov
2018-06-13 13:08 ` [PATCH 4/9] isar-bootstrap-helper: Add parameter to set arch Alexander Smirnov
2018-06-13 13:08 ` [PATCH 5/9] buildchroot-cross: Initial implementation Alexander Smirnov
2018-06-14 11:36 ` Henning Schild
2018-06-15 11:16 ` Alexander Smirnov
2018-06-14 15:55 ` Jan Kiszka
2018-06-15 10:56 ` Alexander Smirnov
2018-06-15 11:12 ` Jan Kiszka
2018-06-17 19:28 ` Alexander Smirnov
2018-06-13 13:08 ` [PATCH 6/9] classes/dpkg*: Relocate dependency from buildchroot Alexander Smirnov
2018-06-14 6:44 ` Jan Kiszka
2018-06-15 10:52 ` Alexander Smirnov
2018-06-13 13:08 ` [PATCH 7/9] classes/dpkg*: Drop hardcoded buildchroot blobs Alexander Smirnov
2018-06-13 13:08 ` [PATCH 8/9] classes/dpkg-cross: Initial implementation Alexander Smirnov
2018-06-13 13:08 ` [PATCH 9/9] [FOR TESTING] libhello: Switch to cross compilation Alexander Smirnov
2018-06-13 13:57 ` [RFC] [PATCH 0/9] Initial cross-compilation support Jan Kiszka
2018-06-14 11:20 ` Henning Schild
2018-06-17 19:41 ` Alexander Smirnov
2018-06-18 7:04 ` Henning Schild
2018-06-14 12:01 ` Henning Schild
2018-06-14 12:04 ` Claudius Heine
2018-06-14 12:24 ` Henning Schild [this message]
2018-06-14 12:36 ` Claudius Heine
2018-06-14 12:30 ` Jan Kiszka
2018-06-14 12:42 ` Claudius Heine
2018-06-14 12:55 ` Claudius Heine
2018-06-15 10:50 ` Alexander Smirnov
2018-06-15 13:17 ` Claudius Heine
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=20180614142418.6e490d83@md1pvb1c.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=ch@denx.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