From: "Liming Gao" <liming.gao@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"tigerliu@zhaoxin.com" <tigerliu@zhaoxin.com>
Subject: Re: [edk2-devel] [edk2] DSC file : override FILE_GUID rule
Date: Thu, 7 Nov 2019 15:16:24 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E53964A@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <0929b662-0447-ed46-1bc7-c53b26804408@redhat.com>
BaseTools can handle the space between them.
Thanks
Liming
> -----Original Message-----
> From: Laszlo Ersek <lersek@redhat.com>
> Sent: Thursday, November 7, 2019 11:12 PM
> To: Gao, Liming <liming.gao@intel.com>; devel@edk2.groups.io; tigerliu@zhaoxin.com
> Subject: Re: [edk2-devel] [edk2] DSC file : override FILE_GUID rule
>
> On 11/07/19 15:59, Gao, Liming wrote:
> > In FDF, you also need to specify this file guid and match the one in DSC. The syntax is like below:
> >
> > INF FILE_GUID= D1D74FE9-7A4E-41D3-A0B3-67F13AD34D94 UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.inf
>
> Thanks! (I assume there is no space character right after "FILE_GUID=".)
>
> Cheers
> Laszlo
>
> > Thanks
> > Liming
> >> -----Original Message-----
> >> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Laszlo Ersek
> >> Sent: Thursday, November 7, 2019 6:56 PM
> >> To: devel@edk2.groups.io; tigerliu@zhaoxin.com
> >> Subject: Re: [edk2-devel] [edk2] DSC file : override FILE_GUID rule
> >>
> >> 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
> >>
> >>
> >>
> >
next prev parent reply other threads:[~2019-11-07 15:16 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
2019-11-07 14:59 ` Liming Gao
2019-11-07 15:12 ` Laszlo Ersek
2019-11-07 15:16 ` Liming Gao [this message]
-- 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=4A89E2EF3DFEDB4C8BFDE51014F606A14E53964A@SHSMSX104.ccr.corp.intel.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