public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 3/3] libhello: Add libhello
Date: Thu, 25 Jan 2018 11:30:07 +0100	[thread overview]
Message-ID: <9afd94bd-eb55-7279-173e-3eb45a6e7483@siemens.com> (raw)
In-Reply-To: <bfd42fb3-dc07-e2bc-4d74-05eea2a5ff96@ilbers.de>

On 2018-01-25 11:11, Alexander Smirnov wrote:
> On 01/25/2018 12:01 PM, Jan Kiszka wrote:
>> On 2018-01-25 09:38, Alexander Smirnov wrote:
>>> 'libhello' package intended to demonstrate Isar build dependencies
>>> between
>>> recipes.
>>>
>>> Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
>>> ---
>>>   meta-isar/recipes-app/example-hello/example-hello.bb |  7 +++++--
>>>   meta-isar/recipes-app/libhello/libhello.bb           | 18
>>> ++++++++++++++++++
>>>   2 files changed, 23 insertions(+), 2 deletions(-)
>>>   create mode 100644 meta-isar/recipes-app/libhello/libhello.bb
>>>
>>> diff --git a/meta-isar/recipes-app/example-hello/example-hello.bb
>>> b/meta-isar/recipes-app/example-hello/example-hello.bb
>>> index 114ee85..19f9d69 100644
>>> --- a/meta-isar/recipes-app/example-hello/example-hello.bb
>>> +++ b/meta-isar/recipes-app/example-hello/example-hello.bb
>>> @@ -8,10 +8,13 @@ DESCRIPTION = "Sample application for ISAR"
>>>   LICENSE = "gpl-2.0"
>>>   LIC_FILES_CHKSUM =
>>> "file://${LAYERDIR_isar}/licenses/COPYING.GPLv2;md5=751419260aa954499f7abaabaa882bbe"
>>>
>>>   -PV = "0.1+g7f35942-1"
>>> +PV = "0.2"
>>> +
>>> +DEPENDS += "libhello"
>>
>> Should be marked as workaround. How hard would it be do extend
>> dpkg[-base?].class with some "DEPENDS += "${@
>> get_deps_from_debian_control()}"?
> 
> I've covered this issue in RFC for reproducibility. Bitbake is
> statically configured tool, so it prepares pipeline *before* start of
> execution. Parsing 'debian/control' assumes that you have already done
> do_fetch() and do_unpack() for specific recipe.
> 

Ah, ok. Too bad.

> But in theory I see only the following for now:
> 
>  - Double bitbake re-run: first step fetch/unpack, second stage parse
> and prepare pipeline.
>  - Modify bitbake.
> 
> I consider this as hack and not as proposal.
> 
> I'll continue this investigation.

Well, if these duplicate dep statements remain limited to self-built
packages, which /should/ remain few as well, we may live with that for
now. Maybe bitbake will eventually learn to update dependencies during
the run so that the two-stage processing wouldn't be needed...

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-01-25 10:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25  8:38 [PATCH 0/3] Implement hello <-> libhello pattern Alexander Smirnov
2018-01-25  8:38 ` [PATCH 1/3] dpkg-base: Add dependecies between Isar recipes Alexander Smirnov
2018-02-05 19:40   ` Jan Kiszka
2018-02-06 10:10     ` chombourger
2018-02-06 20:25       ` Alexander Smirnov
2018-01-25  8:38 ` [PATCH 2/3] build.sh: Install newly built packages Alexander Smirnov
2018-01-31 19:39   ` Jan Kiszka
2018-01-31 19:55     ` Alexander Smirnov
2018-01-31 20:01       ` Jan Kiszka
2018-02-01  7:49         ` Benedikt Niedermayr
2018-02-01  8:07           ` Alexander Smirnov
2018-02-01 10:09             ` Benedikt Niedermayr
2018-02-01 11:37               ` Jan Kiszka
2018-01-25  8:38 ` [PATCH 3/3] libhello: Add libhello Alexander Smirnov
2018-01-25  9:01   ` Jan Kiszka
2018-01-25 10:11     ` Alexander Smirnov
2018-01-25 10:30       ` Jan Kiszka [this message]
2018-01-29 16:14 ` [PATCH 0/3] Implement hello <-> libhello pattern Henning Schild
2018-02-05 21:56 ` Baurzhan Ismagulov

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=9afd94bd-eb55-7279-173e-3eb45a6e7483@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=asmirnov@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