From: Daniel Wang <wonderfly@waymo.com>
To: devel@edk2.groups.io, nathaniel.l.desimone@intel.com
Subject: Re: [edk2-devel] What is a "NULL" library class?
Date: Fri, 29 Jan 2021 09:31:09 -0800 [thread overview]
Message-ID: <CAJmjG29SwCKvOzcKKfabe0ocmxs8J6Xn976gv9ed9pjFa9Q02g@mail.gmail.com> (raw)
In-Reply-To: <MWHPR1101MB2160BAD57389BC93D950D9F0CDB99@MWHPR1101MB2160.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 4533 bytes --]
Thanks for the detailed explanation. Makes sense now.
On Thu, Jan 28, 2021 at 5:43 PM Nate DeSimone <
nathaniel.l.desimone@intel.com> wrote:
> Hi There,
>
> First of all, welcome!
>
> So, “NULL” library classes are conceptually an "anonymous library". It
> enables one to statically link code into a module even if the module
> doesn't directly call functions in that library. All libraries, both
> regular libraries with a declared LibraryClass as well as these anonymous
> libraries, can publish both a constructor and a destructor. The EDK II
> build system will automatically generate a small amount of C code that
> invokes all library constructors before the entry point for the module is
> invoked, and all destructors after the entry point returns. This is useful
> for building statically linked plug-ins.
>
> I think my favorite example of this in-action is the UEFI Shell, here is
> what a typical DSC declaration for the UEFI Shell looks like:
>
> ShellPkg/Application/Shell/Shell.inf {
> <PcdsFixedAtBuild>
> gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|FALSE
> <LibraryClasses>
>
> NULL|ShellPkg/Library/UefiShellLevel1CommandsLib/UefiShellLevel1CommandsLib.inf
>
> NULL|ShellPkg/Library/UefiShellLevel2CommandsLib/UefiShellLevel2CommandsLib.inf
>
> NULL|ShellPkg/Library/UefiShellLevel3CommandsLib/UefiShellLevel3CommandsLib.inf
>
> NULL|ShellPkg/Library/UefiShellDriver1CommandsLib/UefiShellDriver1CommandsLib.inf
>
> NULL|ShellPkg/Library/UefiShellInstall1CommandsLib/UefiShellInstall1CommandsLib.inf
>
> NULL|ShellPkg/Library/UefiShellDebug1CommandsLib/UefiShellDebug1CommandsLib.inf
>
> NULL|ShellPkg/Library/UefiShellNetwork1CommandsLib/UefiShellNetwork1CommandsLib.inf
>
> NULL|ShellPkg/Library/UefiShellNetwork2CommandsLib/UefiShellNetwork2CommandsLib.inf
>
> ShellCommandLib|ShellPkg/Library/UefiShellCommandLib/UefiShellCommandLib.inf
>
> HandleParsingLib|ShellPkg/Library/UefiHandleParsingLib/UefiHandleParsingLib.inf
>
> BcfgCommandLib|ShellPkg/Library/UefiShellBcfgCommandLib/UefiShellBcfgCommandLib.inf
>
> ShellCEntryLib|ShellPkg/Library/UefiShellCEntryLib/UefiShellCEntryLib.inf
> ShellLib|ShellPkg/Library/UefiShellLib/UefiShellLib.inf
> }
>
> If you take a look at
> ShellPkg/Library/UefiShellLevel1CommandsLib/UefiShellLevel1CommandsLib.inf,
> you will see that the constructor for that anonymous library is named
> ShellLevel1CommandsLibConstructor(). Now, let's go and look at the
> definition for ShellLevel1CommandsLibConstructor() in
> ShellPkg/Library/UefiShellLevel1CommandsLib/UefiShellLevel1CommandsLib.c
> and note the following code snippet:
>
> ShellCommandRegisterCommandName(L"stall", ShellCommandRunStall ...
> ShellCommandRegisterCommandName(L"for", ShellCommandRunFor ...
> ShellCommandRegisterCommandName(L"goto", ShellCommandRunGoto ...
> ShellCommandRegisterCommandName(L"if", ShellCommandRunIf ...
> ShellCommandRegisterCommandName(L"shift", ShellCommandRunShift ...
> ShellCommandRegisterCommandName(L"exit", ShellCommandRunExit ...
> ShellCommandRegisterCommandName(L"else", ShellCommandRunElse ...
> ShellCommandRegisterCommandName(L"endif", ShellCommandRunEndIf ...
> ShellCommandRegisterCommandName(L"endfor", ShellCommandRunEndFor ...
>
> This library is installing new commands into the UEFI shell during its
> initialization procedure. This allows one to add custom commands to the
> shell as statically linked built-ins. A typical use case would be
> implementing platform specific diagnostic/recovery utilities.
>
> Hope that helps!
> Nate
>
> > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of
> wonderfly@waymo.com
> > Sent: Thursday, January 28, 2021 10:22 AM
> > To: devel@edk2.groups.io
> > Subject: [edk2-devel] What is a "NULL" library class?
> >
> > Hi,
> >
> > I am super new to EDK2 development so excuse my ignorance. While
> browsing the code base I find a lot places where the keyword "NULL" is used
> in place of a LibraryClass, specifically in DSC files. For example,
> > in edk2/UefiPayloadPkg/UefiPayloadPkgIa32.dsc:
>
> > MdeModulePkg/Core/Dxe/DxeMain.inf {
> > <LibraryClasses>
> >
> NULL|MdeModulePkg/Library/LzmaCustomDecompressLib/LzmaCustomDecompressLib.inf
> > }
> >
> > What does this mean? Does it mean that the LzmaCustomDecompressLib.inf
> library instance is unconditionally linked for this package?
> >
>
>
>
>
>
>
--
Best,
Daniel
[-- Attachment #2: Type: text/html, Size: 5694 bytes --]
prev parent reply other threads:[~2021-01-29 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 18:21 What is a "NULL" library class? wonderfly
2021-01-29 1:42 ` [edk2-devel] " Nate DeSimone
2021-01-29 17:31 ` Daniel Wang [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=CAJmjG29SwCKvOzcKKfabe0ocmxs8J6Xn976gv9ed9pjFa9Q02g@mail.gmail.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