From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] image-hdimg.make: Add PROJECT and PROJECT_VERSION variables.
Date: Fri, 21 Jan 2022 09:44:48 +0100 [thread overview]
Message-ID: <a883a6e9-9299-3a84-db0c-c81535d0fd78@t2data.com> (raw)
In-Reply-To: <Yepsm3UBouuaXknQ@pengutronix.de>
On 1/21/22 9:19 AM, Michael Olbrich wrote:
> On Fri, Jan 14, 2022 at 12:56:47PM +0100, Christian Melki wrote:
>> Ideally, I'd like this to be in the generic genimage env.
>> I need this to be able to name images according to the project.
>
> I don't really like adding random stuff here. And it's easy to expand this
> locally:
>
> IMAGE_HDIMG_ENV += \
> PROJECT=$(PTXCONF_PROJECT) \
> PROJECT_VERSION=$(PTXCONF_PROJECT_VERSION)
>
> In rules/image-hdimg.<something>.make in your BSP since ptxdist-2021.12.0 or in
> rules/post/<something>.make before that.
> So you don't need to overwrite the upstream rule entirely and it's easy to
> maintain.
>
> Michael
>
Mmm.
I do agree that this is pretty random, but it's not random wanting to
name your images according to some project/project-version naming scheme.
I was thinking more like adding project and project_version to the
calling image env. But I was unsure how to do that. Maybe this was
totally unnecessary because the variables already existed in the image
env in some form?
>> Signed-off-by: Christian Melki <christian.melki@t2data.com>
>> ---
>> rules/image-hdimg.make | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/rules/image-hdimg.make b/rules/image-hdimg.make
>> index b470c0fb6..6f0012a85 100644
>> --- a/rules/image-hdimg.make
>> +++ b/rules/image-hdimg.make
>> @@ -57,6 +57,8 @@ IMAGE_HDIMG_ENV = \
>> PARTITION_TABLE_TYPE=$(call ptx/ifdef, PTXCONF_IMAGE_HDIMG_GPT,gpt,mbr) \
>> PARTITION_TYPE_SUFFIX=$(call ptx/ifdef, PTXCONF_IMAGE_HDIMG_GPT,-uuid) \
>> ROOT_PARTITION_TYPE=$(call ptx/ifdef, PTXCONF_IMAGE_HDIMG_GPT,L,0x83) \
>> + PROJECT=$(PTXCONF_PROJECT) \
>> + PROJECT_VERSION=$(PTXCONF_PROJECT_VERSION) \
>> $(IMAGE_HDIMG_BOOTLOADER_ENV)
>>
>> $(IMAGE_HDIMG_IMAGE):
>> --
>> 2.30.2
>>
>>
>> _______________________________________________
>> ptxdist mailing list
>> ptxdist@pengutronix.de
>> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
>>
>
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2022-01-21 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 11:56 Christian Melki
2022-01-21 8:19 ` Michael Olbrich
2022-01-21 8:44 ` Christian Melki [this message]
2022-02-04 13:13 ` Christian Melki
2022-02-04 14:47 ` Michael Olbrich
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=a883a6e9-9299-3a84-db0c-c81535d0fd78@t2data.com \
--to=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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