From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH v2] buildchroot: Add buildchroot dependency for imager
Date: Wed, 14 Jul 2021 09:56:56 +0300 [thread overview]
Message-ID: <b1a1d544-5ac8-b381-7596-65408fb6fb66@ilbers.de> (raw)
In-Reply-To: <33353ffa-63c3-ab32-4dce-05a51174db2c@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 2206 bytes --]
08.07.2021 19:20, Jan Kiszka wrote:
> On 08.07.21 17:21, Anton Mikanovich wrote:
>> To allow do_install_imager_deps depend on proper BUILDCHROOT based on
>> ISAR_CROSS_COMPILE value make dependency to be dynamic.
>>
>> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
>> ---
>> meta/classes/buildchroot.bbclass | 1 +
>> meta/classes/image-tools-extension.bbclass | 1 -
>> 2 files changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/classes/buildchroot.bbclass b/meta/classes/buildchroot.bbclass
>> index 806a29f..1f90768 100644
>> --- a/meta/classes/buildchroot.bbclass
>> +++ b/meta/classes/buildchroot.bbclass
>> @@ -18,6 +18,7 @@ python __anonymous() {
>> rootfs = d.getVar('BUILDCHROOT_HOST_DIR', True)
>>
>> d.setVarFlag('do_apt_fetch', 'depends', dep)
>> + d.setVarFlag('do_install_imager_deps', 'depends', dep)
>> d.setVar('BUILDCHROOT_DIR', rootfs)
>> }
>>
>> diff --git a/meta/classes/image-tools-extension.bbclass b/meta/classes/image-tools-extension.bbclass
>> index 4738479..df32911 100644
>> --- a/meta/classes/image-tools-extension.bbclass
>> +++ b/meta/classes/image-tools-extension.bbclass
>> @@ -14,7 +14,6 @@ IMAGER_INSTALL ??= ""
>> IMAGER_BUILD_DEPS ??= ""
>> DEPENDS += "${IMAGER_BUILD_DEPS}"
>>
>> -do_install_imager_deps[depends] = "buildchroot-target:do_build"
> As explained, this pattern is cleaner than pushing the dependency to the
> required task. Same is true for do_apt_fetch, but that is not in scope
> of this patch.
>
> You should resolve which buildchroot you need and add the dependency
> here, in the proper context.
>
>> do_install_imager_deps[deptask] = "do_deploy_deb"
>> do_install_imager_deps[lockfiles] += "${REPO_ISAR_DIR}/isar.lock"
>> do_install_imager_deps() {
>>
> Jan
>
Ok, to not waste a time on half-measures I've rebuilt both do_apt_fetch
and do_install_imager_deps dependencies in `[PATCH v3 0/3] Fix
imager-buildchroot dependency` patchset. Please, review.
--
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
[-- Attachment #2: Type: text/html, Size: 3071 bytes --]
prev parent reply other threads:[~2021-07-14 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 15:21 Anton Mikanovich
2021-07-08 16:20 ` Jan Kiszka
2021-07-14 6:56 ` Anton Mikanovich [this message]
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=b1a1d544-5ac8-b381-7596-65408fb6fb66@ilbers.de \
--to=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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