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 v3 0/3] Fix imager-buildchroot dependency
Date: Wed, 14 Jul 2021 09:52:31 +0300	[thread overview]
Message-ID: <20210714065234.300300-1-amikan@ilbers.de> (raw)

If using imager with ISAR_CROSS_COMPILE="1" it still depends on
buildchroot-target because of hardcoded flag value. Moreover, there were
no way to depends on buildchroot based on logic placed in python
anonymous function in buildchroot.bbclass. It forced developer to place
dependency set code inside buildchroot choose logic for any tasks like
do_apt_fetch was implemented.
To be able to set dependencies in places where they were implemented but
still take care about cross compile modes we need to put buildchroot
choose result into datastore variable and rely on it later.

Anton Mikanovich (3):
  buildchroot: Introduce buildchroot dependency variable
  buildchroot: Move apt_fetch dependency to dpkg-base
  image: Fix do_install_imager_deps dependency

 meta/classes/buildchroot.bbclass           | 4 ++--
 meta/classes/dpkg-base.bbclass             | 3 +++
 meta/classes/image-tools-extension.bbclass | 2 +-
 3 files changed, 6 insertions(+), 3 deletions(-)

-- 
2.25.1


             reply	other threads:[~2021-07-14  6:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14  6:52 Anton Mikanovich [this message]
2021-07-14  6:52 ` [PATCH v3 1/3] buildchroot: Introduce buildchroot dependency variable Anton Mikanovich
2021-07-14  6:52 ` [PATCH v3 2/3] buildchroot: Move apt_fetch dependency to dpkg-base Anton Mikanovich
2021-07-14  6:52 ` [PATCH v3 3/3] image: Fix do_install_imager_deps dependency Anton Mikanovich
2021-07-26 15:06 ` [PATCH v3 0/3] Fix imager-buildchroot dependency Anton Mikanovich
2021-07-29  7:58   ` 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=20210714065234.300300-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