From: vijai kumar <vijaikumar.kanagarajan@gmail.com>
To: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [RFC PATCH 0/2] U-boot refactor
Date: Mon, 15 Nov 2021 21:40:30 +0530 [thread overview]
Message-ID: <CALLGG_Jv3eqViU5QOkzvw1akYWam1q8RvdsLcBEwMrtEdn9p4Q@mail.gmail.com> (raw)
In-Reply-To: <20211115160642.765371-1-Vijaikumar_Kanagarajan@mentor.com>
On Mon, Nov 15, 2021 at 9:37 PM Vijai Kumar K
<Vijaikumar_Kanagarajan@mentor.com> wrote:
>
> Hi,
>
> This series refactors u-boot recipe to build selective packages
> based on DEB_BUILD_PROFILES.
>
> This solves 2 problems(kind of related).
>
> 1. Tools were always built irrespective of whether we ship them or not.
> 2. libssl-dev package is needed only when we cross compile tools.
> Having this change, makes sure the dependency is only included when
> it is actually needed.
>
> P1 drops the U_BOOT_TOOLS_PACKAGE variable and introduces
> U_BOOT_BUILD_PROFILES in which we can specify which package to
> build(tools, dev, config).
>
> P2 makes sure libssl-dev is included only when it is needed.
Ah. This already needs V2. Need to take care of the below line
u-boot-custom.inc:13:PROVIDES += "${@'u-boot-tools' if
d.getVar('U_BOOT_TOOLS_PACKAGE') == '1' else ''}"
Will wait for review comments and club the changes, if any.
Thanks,
Vijai Kumar K
>
>
> Thanks,
> Vijai Kumar K
>
>
> Vijai Kumar K (2):
> u-boot: Switch to use DEB_BUILD_PROFILES
> meta/u-boot: Include libssl-dev only when building tools
>
> .../u-boot/u-boot-de0-nano-soc_2021.10.bb | 3 +-
> .../u-boot/u-boot-stm32mp15x_2021.10.bb | 2 ++
> .../u-boot/files/debian/control.tmpl | 13 ++++++++
> meta/recipes-bsp/u-boot/files/debian/rules | 9 +++++-
> meta/recipes-bsp/u-boot/u-boot-custom.inc | 32 ++++++-------------
> 5 files changed, 34 insertions(+), 25 deletions(-)
>
> --
> 2.25.1
>
> --
> You received this message because you are subscribed to the Google Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/20211115160642.765371-1-Vijaikumar_Kanagarajan%40mentor.com.
next prev parent reply other threads:[~2021-11-15 16:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 16:06 Vijai Kumar K
2021-11-15 16:06 ` [RFC PATCH 1/2] u-boot: Switch to use DEB_BUILD_PROFILES Vijai Kumar K
2021-11-15 16:44 ` Jan Kiszka
2021-11-16 8:42 ` vijai kumar
2021-11-16 15:02 ` Gylstorff Quirin
2021-11-17 5:52 ` vijai kumar
2021-11-15 16:06 ` [RFC PATCH 2/2] meta/u-boot: Include libssl-dev only when building tools Vijai Kumar K
2021-11-15 16:46 ` Jan Kiszka
2021-11-16 8:44 ` vijai kumar
2021-11-15 16:10 ` vijai kumar [this message]
2021-11-16 9:51 ` [PATCH v2 0/2] U-boot refactor Vijai Kumar K
2021-11-16 9:51 ` [PATCH v2 1/2] u-boot: Switch to use DEB_BUILD_PROFILES Vijai Kumar K
2021-11-16 15:40 ` Jan Kiszka
2021-11-17 5:56 ` vijai kumar
2021-11-16 9:51 ` [PATCH v2 2/2] meta/u-boot: Include libssl-dev only when building tools 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=CALLGG_Jv3eqViU5QOkzvw1akYWam1q8RvdsLcBEwMrtEdn9p4Q@mail.gmail.com \
--to=vijaikumar.kanagarajan@gmail.com \
--cc=Vijaikumar_Kanagarajan@mentor.com \
--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