public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Udit Kumar" <udit.kumar@nxp.com>
To: Laszlo Ersek <lersek@redhat.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [EXT] Re: [edk2-devel] Printing git commit in build
Date: Thu, 13 Jun 2019 06:40:12 +0000	[thread overview]
Message-ID: <VI1PR04MB4640F5DC003B6B74CC8B0B8191EF0@VI1PR04MB4640.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1cb32f45-fedb-cec2-2d6a-8d5f90efc475@redhat.com>

Thanks Laszlo

> -----Original Message-----
> From: Laszlo Ersek <lersek@redhat.com>
> Sent: Thursday, June 6, 2019 1:55 PM
> To: devel@edk2.groups.io; Udit Kumar <udit.kumar@nxp.com>
> Subject: [EXT] Re: [edk2-devel] Printing git commit in build
> 
> Caution: EXT Email
> 
> On 06/06/19 07:38, Udit Kumar wrote:
> > Dear Community,
> >
> > I like to print git commit id, which printing UEFI firmware build information.
> > Could you help, how I can collect ' git describe' information in C file.
> 
> I think you should be able to do this in the PREBUILD hook in the DSC file.
> (Run "git describe" in a script for generating a simple C source file.)
> 
> 
> Another option would be to introduce a PCD in your platform package DEC
> file, with datum type (VOID*) and access method FixedAtBuild. For example:
> 
> [PcdsFixedAtBuild]
>   gMyPlatformPkgTokenSpaceGuid.PcdBuildIdentifier|""|VOID*|<token>
> 
> and when you build your platform DSC, you could pass the following option
> to the "build" utility:
> 
>   --pcd=gMyPlatformPkgTokenSpaceGuid.PcdBuildIdentifier="$(git
> describe)"
> 
> Thanks
> Laszlo

      reply	other threads:[~2019-06-13  6:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06  5:38 Printing git commit in build udit.kumar
2019-06-06  8:25 ` [edk2-devel] " Laszlo Ersek
2019-06-13  6:40   ` Udit Kumar [this message]

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-list 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=VI1PR04MB4640F5DC003B6B74CC8B0B8191EF0@VI1PR04MB4640.eurprd04.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /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