From: Gylstorff Quirin <quirin.gylstorff@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
vijai kumar <vijaikumar.kanagarajan@gmail.com>
Cc: 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 09:34:13 +0100 [thread overview]
Message-ID: <d1f7cd88-a44e-24a6-5aa4-c07563e6f61c@siemens.com> (raw)
In-Reply-To: <da317166-83e2-56b2-6735-be50fb92a614@siemens.com>
On 11/25/21 5:34 PM, Jan Kiszka wrote:
> 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.
>
I think that pattern looks much better - if it works.
Quirin
> Jan
-
next prev parent reply other threads:[~2021-11-26 8:34 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
2021-11-26 6:33 ` vijai kumar
2021-11-26 6:56 ` vijai kumar
2021-11-26 8:34 ` Gylstorff Quirin [this message]
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=d1f7cd88-a44e-24a6-5aa4-c07563e6f61c@siemens.com \
--to=quirin.gylstorff@siemens.com \
--cc=Vijaikumar_Kanagarajan@mentor.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@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