public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH 0/3] Introduce Debian dependencies and provides helper
Date: Thu, 21 Sep 2023 09:32:44 +0300	[thread overview]
Message-ID: <20230921063247.3114251-1-amikan@ilbers.de> (raw)

Package information from debian/control file is not available when
bitbake prepares dependency tree on beginning of the build operation.
So developers should manually set at least DEPENDS and PROVIDES values.

This helper script can do the following:
1. Scan for all recipes and add missed PROVIDES values.
2. Scan for target dependencies and add missed DEPENDS values.

Missed values are added as bbappend files near the original recipes.

Usage:
$ ../scripts/explore.py [ all | deps | provides ] mc:qemuamd64-bullseye:isar-image-base

It supposed to be executed inside build dir and requires python3-apt package to
be installed. Running PROVIDES scanning also requires COMPATIBLE_MACHINE to be
used in machine-specific recipes, so there will be no way to build them for
incompatible target.

This patchset should be placed on top of:
[PATCH 0/5] Separate prebuild activities

Anton Mikanovich (3):
  conf: Enable bbappends
  isar: Add dependency explorer
  isar: Add provides explorer

 meta-isar/conf/layer.conf |   2 +-
 meta-test/conf/layer.conf |   2 +-
 meta/conf/layer.conf      |   2 +-
 scripts/explore.py        | 264 ++++++++++++++++++++++++++++++++++++++
 4 files changed, 267 insertions(+), 3 deletions(-)
 create mode 100755 scripts/explore.py

-- 
2.34.1


             reply	other threads:[~2023-09-21  6:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21  6:32 Anton Mikanovich [this message]
2023-09-21  6:32 ` [PATCH 1/3] conf: Enable bbappends Anton Mikanovich
2023-09-21  6:32 ` [PATCH 2/3] isar: Add dependency explorer Anton Mikanovich
2023-09-21  6:32 ` [PATCH 3/3] isar: Add provides explorer Anton Mikanovich

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=20230921063247.3114251-1-amikan@ilbers.de \
    --to=amikan@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