public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Adriaan Schmidt <adriaan.schmidt@siemens.com>
To: <isar-users@googlegroups.com>
Cc: Adriaan Schmidt <adriaan.schmidt@siemens.com>
Subject: [PATCH v3 0/3] sdk: make SDK an image
Date: Fri, 17 Dec 2021 10:10:27 +0100	[thread overview]
Message-ID: <20211217091030.474380-1-adriaan.schmidt@siemens.com> (raw)

Here's my new proposal to refactor the SDK generation.
For all recipes inheriting image.bbclass, this automatically provides
a *-sdk bitbake target. This can be built to generate the SDK, and
in addition the original build target has -cpopulate_sdk to preserve
the current interface to the user.

As SDKs are very image-specific, I changed SDKCHROOT_DIR (which is
the sdk deploy location below tmp/deploy/sdkchroot) to include the
target image name and ${MACHINE} instead of ${DISTRO}-${DISTROARCH}.
Seemed right to me, but we can discuss.

Two other commits included:
- remove image suffix: already in discussion. This simplifies things,
  and at least in my limited local tests does not cause any problems.
- change how image tasks are added. This is just to enable testing
  the new SDK feature stand-alone.

Adriaan Schmidt (3):
  image: remove IMAGE_SUFFIX
  image: refactor SDK
  image: include all types and add tasks on demand

 meta/classes/container-img.bbclass            |   2 -
 meta/classes/cpiogz-img.bbclass               |   1 -
 meta/classes/ext4-img.bbclass                 |   1 -
 meta/classes/fit-img.bbclass                  |   2 +-
 meta/classes/image-sdk-extension.bbclass      |  87 -----------
 meta/classes/image.bbclass                    |  32 +++-
 meta/classes/sdk.bbclass                      | 137 ++++++++++++++++++
 meta/classes/targz-img.bbclass                |   1 -
 meta/classes/ubi-img.bbclass                  |   4 +-
 meta/classes/ubifs-img.bbclass                |   3 +-
 meta/classes/wic-img.bbclass                  |   1 -
 .../{sdkchroot => sdk-files}/files/README.sdk |   0
 .../files/configscript.sh                     |   0
 .../files/gcc-sysroot-wrapper.sh              |   0
 .../files/relocate-sdk.sh                     |   0
 meta/recipes-devtools/sdk-files/sdk-files.bb  |  26 ++++
 meta/recipes-devtools/sdkchroot/sdkchroot.bb  |  78 ----------
 17 files changed, 192 insertions(+), 183 deletions(-)
 delete mode 100644 meta/classes/image-sdk-extension.bbclass
 create mode 100644 meta/classes/sdk.bbclass
 rename meta/recipes-devtools/{sdkchroot => sdk-files}/files/README.sdk (100%)
 rename meta/recipes-devtools/{sdkchroot => sdk-files}/files/configscript.sh (100%)
 rename meta/recipes-devtools/{sdkchroot => sdk-files}/files/gcc-sysroot-wrapper.sh (100%)
 rename meta/recipes-devtools/{sdkchroot => sdk-files}/files/relocate-sdk.sh (100%)
 create mode 100644 meta/recipes-devtools/sdk-files/sdk-files.bb
 delete mode 100644 meta/recipes-devtools/sdkchroot/sdkchroot.bb

-- 
2.30.2


             reply	other threads:[~2021-12-17  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17  9:10 Adriaan Schmidt [this message]
2021-12-17  9:10 ` [PATCH v3 1/3] image: remove IMAGE_SUFFIX Adriaan Schmidt
2021-12-17 10:22   ` Jan Kiszka
2021-12-17  9:10 ` [PATCH v3 2/3] image: refactor SDK Adriaan Schmidt
2021-12-17  9:10 ` [PATCH v3 3/3] image: include all types and add tasks on demand Adriaan Schmidt

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=20211217091030.474380-1-adriaan.schmidt@siemens.com \
    --to=adriaan.schmidt@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