public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: vijai kumar <vijaikumar.kanagarajan@gmail.com>
Cc: Gylstorff Quirin <quirin.gylstorff@siemens.com>,
	Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 3/4] meta: u-boot: Prepare for newer versions
Date: Fri, 26 Nov 2021 07:29:47 +0100	[thread overview]
Message-ID: <adec9748-43bd-d6bd-5a44-1640ee744784@siemens.com> (raw)
In-Reply-To: <CALLGG_+PQ9iYRBJRAtO--2cQxcJ-9FyjkVyFwzpmeQ1E2xGc+A@mail.gmail.com>

On 26.11.21 07:07, vijai kumar wrote:
> On Thu, Nov 25, 2021 at 10:04 PM Jan Kiszka <jan.kiszka@siemens.com> wrote:
>>
>> On 25.11.21 17:27, vijai kumar wrote:
>>> On Thu, Nov 25, 2021 at 12:12 PM vijai kumar
>>> <vijaikumar.kanagarajan@gmail.com> wrote:
>>>>
>>>> On Tue, Nov 23, 2021 at 3:24 PM Gylstorff Quirin
>>>> <quirin.gylstorff@siemens.com> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> On 11/22/21 4:26 PM, Vijai Kumar K wrote:
>>>>>> Newer versions of u-boot require libssl-dev:native for compilation.
>>>>>> It also needs libssl-dev of the host architecture for cross compilation
>>>>>> of tools.
>>>>>>
>>>>>> Signed-off-by: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
>>>>>> ---
>>>>>>   meta/recipes-bsp/u-boot/u-boot-custom.inc | 4 +++-
>>>>>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>>>>>
>>>>>> diff --git a/meta/recipes-bsp/u-boot/u-boot-custom.inc b/meta/recipes-bsp/u-boot/u-boot-custom.inc
>>>>>> index 5198809..cfae0e2 100644
>>>>>> --- a/meta/recipes-bsp/u-boot/u-boot-custom.inc
>>>>>> +++ b/meta/recipes-bsp/u-boot/u-boot-custom.inc
>>>>>> @@ -41,7 +41,9 @@ python() {
>>>>>>               d.setVar('U_BOOT_BUILD_PROFILES_remove', "config")
>>>>>>   }
>>>>>>
>>>>>> -DEBIAN_BUILD_DEPENDS ?= "bc, bison, flex, device-tree-compiler, git"
>>>>>> +DEBIAN_BUILD_DEPENDS ?= "bc, bison, flex, device-tree-compiler, git, libssl-dev:native"
>>>>>> +DEBIAN_BUILD_DEPENDS += "${@', libssl-dev' \
>>>>>> +     if bb.utils.contains('U_BOOT_BUILD_PROFILES', 'tools', 1, 0, d) else ''}"
>>>>>
>>>>> Is there are reason why you didn't use `Build-Depends syntax extension`
>>>>> from[1]?
>>>>>
>>>> Hi Quirin,
>>>>
>>>> Yes. There was. The previous version of patch depends on
>>>> ISAR_CROSS_COMPILE as well.
>>>>
>>>> Guess there is nothing stopping us now. But, wondering if we can start
>>>> introducing it via some
>>>> example app with some documentation so that basic users are not
>>>> puzzled on seeing that line in
>>>> a recipe.
>>>>
>>>> Also, we could define a whole new variable to help recipe writers to
>>>> define profiles and seamlessly
>>>> use them without the need to explicitly export DEB_BUILD_PROFILES in
>>>> the recipe's dpkg_runbuild
>>>>
>>>> Now that we are serious enough, we should probably take care of your
>>>> earlier comment
>>>> as well on following the standard. So that we don't conflict with
>>>> Debian's predefined variables in case
>>>> we decided to build a package fetched from apt:// and wanted to make
>>>> use of its profile settings.
>>>>
>>>> Still need to look further but these are my initial thoughts. I could
>>>> probably send some patches for review in
>>>> coming days.
>>>>
>>>> For now, maybe we should call it and use pkg.uboot.tools instead of
>>>> tools here so that we don't
>>>> find something in that implementation that requires us to change this
>>>> in future, possibly breaking
>>>> u-boot / or the need to provide compatibility.
>>>>
>>>> Thoughts?
>>>
>>> OTOH, This could still go in. Since the design I am thinking of is not
>>> finalized and might take some discussions in the list, there is no
>>> point in holding this back.
>>>
>>
>> I think Quirin was just asking for
>>
>> DEBIAN_BUILD_DEPENDS ?= "bc, bison, flex, device-tree-compiler, git, \
>>         libssl-dev:native, libssl-dev <tools>"
>>
>> rather than using bitbake logic. If that also works, would be more elegant.
> 
> Yes, that also works. But just a bit difficult to read for normal users.

It's more Debian-style, thus to be preferred according to Isar principles.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

  reply	other threads:[~2021-11-26  6:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 15:26 [PATCH v2 0/4] U-boot refactor and uprevision Vijai Kumar K
2021-11-22 15:26 ` [PATCH v2 1/4] u-boot: Switch to use DEB_BUILD_PROFILES Vijai Kumar K
2021-11-22 15:26 ` [PATCH v2 2/4] meta-isar: u-boot: Migrate to U_BOOT_BUILD_PROFILES Vijai Kumar K
2021-11-22 15:26 ` [PATCH v2 3/4] meta: u-boot: Prepare for newer versions Vijai Kumar K
2021-11-23  9:54   ` Gylstorff Quirin
2021-11-25  6:42     ` vijai kumar
2021-11-25 16:27       ` vijai kumar
2021-11-25 16:34         ` Jan Kiszka
2021-11-26  6:07           ` vijai kumar
2021-11-26  6:29             ` Jan Kiszka [this message]
2021-11-26  6:33               ` vijai kumar
2021-11-26  6:56             ` vijai kumar
2021-11-26  8:34           ` Gylstorff Quirin
2021-11-22 15:26 ` [PATCH v2 4/4] meta-isar: u-boot: Update to 2021.10 Vijai Kumar K

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=adec9748-43bd-d6bd-5a44-1640ee744784@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=Vijaikumar_Kanagarajan@mentor.com \
    --cc=isar-users@googlegroups.com \
    --cc=quirin.gylstorff@siemens.com \
    --cc=vijaikumar.kanagarajan@gmail.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