Laurie Jarlstrom edited this page Jun 29, 2017 · 6 revisions

The Module Development Environment Package (MdePkg) is a special package as it is the minimum infrastructure required to build a module. A module may require extra packages to be constructed but all modules are based on the MdePkg. By keeping the MdePkg very stable, it effectively becomes a module or device driver kit for building modules that can work with various sets of packages.

The MdePkg provides all definitions(including functions, MACROs, structures and library classes) and libraries instances, which are defined in the MdePkg. The latest MdePkg .chm files will document these definitions and can be found in the latest UDK releases.

It also provides the definitions(including PPIs/PROTOCOLs/GUIDs) of EFI1.10/UEFI2.x/PI1.x and other Industry Standards.

The MdePkg enables the construction of a range of module types. The MdePkg can be used alone or in combination with other packages to produce modules. The MdePkg can produce stand-alone modules defined as base that only use resources defined in MdePkg that are of type base. Base modules allow you to write portable C code that can be easily ported to any environment. The MdePkg can be used to write SEC in C code. The MdePkg package can also produce UEFI drivers or UEFI applications that conform to either the EFI 1.10 or the UEFI 2.x specifications. The MdePkg can also build UEFI drivers or applications based on the EDK II build environment described in the EDK II Specifications.

The latest MdePkg .chm files will document all the details on the definitions (including PPIs/PROTOCOLs/GUIDs and library classes) and libraries instances associated with the MdePkg package. To download the latest .chm files see UDK for the current release.

Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.