public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Alexander Smirnov <asmirnov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH 3/3] libhello: Add libhello
Date: Thu, 25 Jan 2018 13:11:34 +0300	[thread overview]
Message-ID: <bfd42fb3-dc07-e2bc-4d74-05eea2a5ff96@ilbers.de> (raw)
In-Reply-To: <04dedcd3-4920-f829-0148-e519ebd24eb5@siemens.com>

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.

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.

Alex

  We probably also need some translation
> from the debian package name / aliases into bitbake PROVIDES variables.
> 
> Jan
> 
>>   
>>   SRC_URI = "git://github.com/ilbers/hello.git;branch=devel;protocol=https"
>> -SRCREV = "5c0ae73fdc97d80b6726e602a1fa0ef00c2c012a"
>> +SRCREV = "ffca497b3f8157efe3eb6fab97a88045142591ae"
>> +
>>   
>>   SRC_DIR = "git"
>>   
>> diff --git a/meta-isar/recipes-app/libhello/libhello.bb b/meta-isar/recipes-app/libhello/libhello.bb
>> new file mode 100644
>> index 0000000..4caaf2d
>> --- /dev/null
>> +++ b/meta-isar/recipes-app/libhello/libhello.bb
>> @@ -0,0 +1,18 @@
>> +# Sample shared library
>> +#
>> +# This software is a part of ISAR.
>> +# Copyright (C) 2017-2018 ilbers GmbH
>> +
>> +DESCRIPTION = "Sample shared library for ISAR"
>> +
>> +LICENSE = "gpl-2.0"
>> +LIC_FILES_CHKSUM = "file://${LAYERDIR_isar}/licenses/COPYING.GPLv2;md5=751419260aa954499f7abaabaa882bbe"
>> +
>> +PV = "0.1"
>> +
>> +SRC_URI = "git://github.com/alexbluesman/libhello.git;protocol=https"
>> +SRCREV = "1671f0287fe0bca8937f687f53a3bd05c9e2d9c2"
>> +
>> +SRC_DIR = "git"
>> +
>> +inherit dpkg
>>
>

  reply	other threads:[~2018-01-25 10:11 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 [this message]
2018-01-25 10:30       ` Jan Kiszka
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=bfd42fb3-dc07-e2bc-4d74-05eea2a5ff96@ilbers.de \
    --to=asmirnov@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