From: Henning Schild <henning.schild@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Henning Schild <henning.schild@siemens.com>
Subject: [PATCH 0/2] Straighten cross names
Date: Tue, 11 Sep 2018 12:16:03 +0200 [thread overview]
Message-ID: <20180911101605.21977-1-henning.schild@siemens.com> (raw)
With the recent introduction of cross building we introduced confusing
names in Isar. The following article describes how the names should be
in Debian, which is probably what we should follow.
https://wiki.debian.org/CrossCompiling#Nomenclature
This series partially fixes the names. Applying it without changing the
rest would probably just increase the confusion. I am still posting it
as a starting point and to point out that there currently is a naming
issue in Isar.
Henning Schild (2):
cross: use env variables instead of switches
build-kernel: fix the cross compile arch naming
meta/classes/dpkg.bbclass | 8 ++++++--
meta/recipes-devtools/buildchroot/files/build.sh | 2 +-
meta/recipes-devtools/buildchroot/files/common.sh | 13 -------------
meta/recipes-devtools/buildchroot/files/deps.sh | 2 +-
meta/recipes-kernel/linux/files/build-kernel.sh | 18 +++++++++---------
meta/recipes-kernel/linux/linux-custom.inc | 4 ++--
6 files changed, 19 insertions(+), 28 deletions(-)
--
2.16.4
next reply other threads:[~2018-09-11 10:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 10:16 Henning Schild [this message]
2018-09-11 10:16 ` [PATCH 1/2] cross: use env variables instead of switches Henning Schild
2018-09-21 12:55 ` [PATCHv2 " Henning Schild
2018-09-21 13:08 ` Henning Schild
2018-09-27 7:12 ` Maxim Yu. Osipov
2018-09-27 7:15 ` Jan Kiszka
2018-09-28 10:47 ` Henning Schild
2018-09-11 10:16 ` [PATCH 2/2] build-kernel: fix the cross compile arch naming Henning Schild
2018-09-11 12:10 ` Jan Kiszka
2018-09-11 12:20 ` Henning Schild
2018-09-21 10:00 ` [PATCH 0/2] Straighten cross names Maxim Yu. Osipov
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=20180911101605.21977-1-henning.schild@siemens.com \
--to=henning.schild@siemens.com \
--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