public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, tigerliu@zhaoxin.com
Subject: Re: [edk2-devel] [edk2] DSC file : override FILE_GUID rule
Date: Thu, 7 Nov 2019 11:56:06 +0100	[thread overview]
Message-ID: <dbebafb1-ca92-1f33-ec24-b89f3f85354d@redhat.com> (raw)
In-Reply-To: <44ad448fba40477f83fcb614df6880b7@zhaoxin.com>

On 11/07/19 05:51, Tiger Liu(BJ-RD) wrote:
> Dear All:
> I have a question about FILE_GUID override rule in dsc file.
> For example:
>   ......
>   UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.inf {
>     <Defines>
>       FILE_GUID = D1D74FE9-7A4E-41D3-A0B3-67F13AD34D94
>     ......
>   }
> 
> Usually, will define FILE_GUID in PiSmmCpuDxeSmm.inf .
> 
> Why override it in dsc file?

IIRC, such overrides allow the platform DSC file to build the same
module multiple times, most likely with other overrides too (such as PCD
and lib class resolution). The resultant binaries will not conflict in
any firmware volume / firmware file-system, by FILE_GUID.

I don't remember the syntax, to be used in the FDF file, for refering to
all of the builds of the same module INF file.

Thanks
Laszlo


  reply	other threads:[~2019-11-07 10:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07  4:51 [edk2-devel] [edk2] DSC file : override FILE_GUID rule Tiger Liu(BJ-RD)
2019-11-07 10:56 ` Laszlo Ersek [this message]
2019-11-07 14:59   ` Liming Gao
2019-11-07 15:12     ` Laszlo Ersek
2019-11-07 15:16       ` Liming Gao
  -- strict thread matches above, loose matches on Subject: below --
2019-11-08  2:51 Tiger Liu(BJ-RD)

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=dbebafb1-ca92-1f33-ec24-b89f3f85354d@redhat.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