public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
	"edk2-lists@mc2research.org" <edk2-lists@mc2research.org>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Undefined types referenced in MdePkg
Date: Thu, 2 Aug 2018 20:24:04 +0200	[thread overview]
Message-ID: <21479902-a40c-2eb0-029d-295964b60b19@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E2C4A78@SHSMSX104.ccr.corp.intel.com>

On 08/02/18 15:05, Gao, Liming wrote:
> MdePkg provides the basic module type header file, such as PiPei.h,
> PiDxe.h, Uefi.h. PiPei.h and PiDxe.h will include the basic PI
> definition. They have included PiHob.h and PiFirmwareVolume.h. 
> Because the module type header file is included into AutoGen.h based
> on the module type. And, AutoGen.h is always included by compiler
> option. So, in edk2 build system, there is no issue to include
> HobLib.h and Protocol/FirmwareVolume2.h in source files.

Thanks, this is helpful!
Laszlo


      reply	other threads:[~2018-08-02 18:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-01 17:49 Undefined types referenced in MdePkg edk2-lists
2018-08-01 21:55 ` Laszlo Ersek
2018-08-01 23:51   ` edk2-lists
2018-08-02 13:05     ` Gao, Liming
2018-08-02 18:24       ` Laszlo Ersek [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=21479902-a40c-2eb0-029d-295964b60b19@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