From: "Noah Hütter" <noahhuetter@gmail.com>
To: Arnout Vandecappelle <arnout@mind.be>,
Alistair Francis <alistair23@gmail.com>
Cc: Alistair Francis <alistair@alistair23.me>,
buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] boot/opensbi: introduce BR2_TARGET_OPENSBI_CUSTOM_MAKEOPTS
Date: Fri, 13 May 2022 11:42:05 +0200 [thread overview]
Message-ID: <34bf150f-42b9-1f32-e693-5cc011afc609@gmail.com> (raw)
In-Reply-To: <e7ca5854-27eb-a416-1783-15193b0e898b@mind.be>
[-- Attachment #1.1.1: Type: text/plain, Size: 3022 bytes --]
On 5/12/22 23:57, Arnout Vandecappelle wrote:
>
>
> On 12/05/2022 08:50, Noah Hütter wrote:
>> Hi Alistair,
>>
>> Is there any action needed from my side to get this committed?
>
> It's just one of the +-200 pending patches that are not trivial.
Thanks for the update, I didn't want to put pressure on anyone, I'm a
first time contributor and want to make no mistakes :).
>>
>> Noah
>>
>> On 4/28/22 00:55, Alistair Francis wrote:
>>> On Wed, Apr 27, 2022 at 11:14 PM Noah Huetter <noahhuetter@gmail.com>
>>> wrote:
>>>>
>>>> Signed-off-by: Noah Huetter <noahhuetter@gmail.com>
>>>
>>> Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
>>>
>>> Alistair
>>>
>>>> ---
>>>> boot/opensbi/Config.in | 6 ++++++
>>>> boot/opensbi/opensbi.mk | 3 ++-
>>>> 2 files changed, 8 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/boot/opensbi/Config.in b/boot/opensbi/Config.in
>>>> index f1443498d9..ff095ea800 100644
>>>> --- a/boot/opensbi/Config.in
>>>> +++ b/boot/opensbi/Config.in
>>>> @@ -119,4 +119,10 @@ config BR2_TARGET_OPENSBI_FW_FDT_PATH
>>>> must be set in the U-Boot configuration for this file to be
>>>> produced.
>>>>
>>>> +config BR2_TARGET_OPENSBI_CUSTOM_MAKEOPTS
>>>> + string "Custom make options"
>>>> + help
>>>> + List of custom make options passed at build time. Can be
>>>> + used for example to pass a BUILD_INFO= value.
>
> In this case, it's not trivial because the use case is not clear.
> Almost every package has some random make, cmake, meson or whatever
> options that you could pass to it. What makes OpenSBI so special that
> you need to pass a freeform list of additional options?
In my specific case as described in the help, the value to `BUILD_INFO`.
From looking at other packages I deduced that the _CUSTOM_MAKEOPTS is a
common config to packages and added it to OpenSBI. Did I overlook something?
Best,
Noah
>>>> +
>>>> endif
>>>> diff --git a/boot/opensbi/opensbi.mk b/boot/opensbi/opensbi.mk
>>>> index 8e055633a8..d007ae1299 100644
>>>> --- a/boot/opensbi/opensbi.mk
>>>> +++ b/boot/opensbi/opensbi.mk
>>>> @@ -31,7 +31,8 @@ BR_NO_CHECK_HASH_FOR += $(OPENSBI_SOURCE)
>>>> endif
>>>>
>>>> OPENSBI_MAKE_ENV = \
>>>> - CROSS_COMPILE=$(TARGET_CROSS)
>>>> + CROSS_COMPILE=$(TARGET_CROSS) \
>>>> + $(call qstrip,$(BR2_TARGET_OPENSBI_CUSTOM_MAKEOPTS))
>>>>
>>>> OPENSBI_PLAT = $(call qstrip,$(BR2_TARGET_OPENSBI_PLAT))
>>>> ifneq ($(OPENSBI_PLAT),)
>>>> --
>>>> 2.35.1
>>>>
>>>> _______________________________________________
>>>> buildroot mailing list
>>>> buildroot@buildroot.org
>>>> https://lists.buildroot.org/mailman/listinfo/buildroot
>>
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot@buildroot.org
>> https://lists.buildroot.org/mailman/listinfo/buildroot
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-13 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 13:14 [Buildroot] [PATCH 1/1] boot/opensbi: introduce BR2_TARGET_OPENSBI_CUSTOM_MAKEOPTS Noah Huetter
2022-04-27 22:55 ` Alistair Francis
2022-05-12 6:50 ` Noah Hütter
2022-05-12 21:57 ` Arnout Vandecappelle
2022-05-13 9:42 ` Noah Hütter [this message]
2022-05-13 20:05 ` Arnout Vandecappelle
2022-07-26 22:15 ` Thomas Petazzoni via buildroot
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=34bf150f-42b9-1f32-e693-5cc011afc609@gmail.com \
--to=noahhuetter@gmail.com \
--cc=alistair23@gmail.com \
--cc=alistair@alistair23.me \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
/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