From: Henning Schild <henning.schild@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/3] Implement hello <-> libhello pattern
Date: Mon, 29 Jan 2018 17:14:19 +0100 [thread overview]
Message-ID: <20180129171419.0d6c57b1@mmd1pvb1c.ad001.siemens.net> (raw)
In-Reply-To: <20180125083851.5887-1-asmirnov@ilbers.de>
Am Thu, 25 Jan 2018 11:38:48 +0300
schrieb Alexander Smirnov <asmirnov@ilbers.de>:
> This series intended to add Isar build dependencies between recipes.
Nice, this is truly needed!
> Overall concept:
> - A new recipe is added to Isar - libhello.
> - 'hello' application was modified, not it has 'libhello-dev' as
> build dependency.
>
> Issues:
> - At the moment there is no support for Isar-apt in buildchroot, so
> no clear way to install 'libhello-dev' during building 'hello'
> application. To satisfy it for now, I've added line to install
> newly built packages right after compilation (see patch 2).
>
> I'm going to improve Isar-apt support to avoid the issue mentioned
> above. Isar-apt looks for me as a bit complicated change, so I'd
> suggest to commit this series as intermediate small step.
I would not like to see patch2 being merged, this is just running
deeper into dept. People that have an urgent need for that can always
"dpkg -i" in their recipes, that is already happening. So when we come
up with a solution, it should be the right one and not centralizing a
known-to-work hack.
Henning
> NOTE: please don't pay attention to SRC_URI. I'm sharing my current
> tested state. Before merging this to Isar I'll update hello/libhello
> repositories and point SRC_URIs to master branches.
>
> Alex
>
> Alexander Smirnov (3):
> dpkg-base: Add dependecies between Isar recipes
> build.sh: Install newly built packages
> libhello: Add libhello
>
> meta-isar/recipes-app/example-hello/example-hello.bb | 7 +++++--
> meta-isar/recipes-app/libhello/libhello.bb | 18
> ++++++++++++++++++
> meta/classes/dpkg-base.bbclass | 4 ++++
> meta/recipes-devtools/buildchroot/files/build.sh | 3 +++ 4 files
> changed, 30 insertions(+), 2 deletions(-) create mode 100644
> meta-isar/recipes-app/libhello/libhello.bb
>
next prev parent reply other threads:[~2018-01-29 16:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 8:38 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
2018-01-29 16:14 ` Henning Schild [this message]
2018-02-05 21:56 ` [PATCH 0/3] Implement hello <-> libhello pattern 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=20180129171419.0d6c57b1@mmd1pvb1c.ad001.siemens.net \
--to=henning.schild@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