12.07.2015 Views

EDK II Module Writer's Guide - Intel

EDK II Module Writer's Guide - Intel

EDK II Module Writer's Guide - Intel

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

warning C4013: 'FeaturePcdGet' undefined; assuming extern returning intPcdLib.h is missing in the module source code. When PCD is used in amodule, PcdLib APIs are referenced to access the PCD. The PcdLib headerfile must included in this module source code.error 0010: File name case mismatchMde<strong>Module</strong>Pkg\Application\Helloworld\HelloWorld.infMde<strong>Module</strong>Pkg\Application\HelloWorld\HelloWorld.inf [in file system]Note: Lower case ‘w’ in’ Helloworld’, in the first pathThe module INF file path specified in the DSC is not same as its file pathin the file system. The same error may occur for the source file pathspecified in the [Source] section of a module INF. According to the errorinformation, the file path in the DSC or INF needs to be corrected to itsfile path in file system. All files must have their name and case set thesame in the meta data files as in the file system.error 4000: Instance of library class [NameOneLib] is not found consumed bymodule [Mde<strong>Module</strong>Pkg\Application\HelloWorld\HelloWorld.inf]The DSC file is missing a library class to library instance mapping for thegiven library. If the module doesn’t depend on the library class, theunused library class can be removed from the [LibraryClasses] section ofmodule INF to fix this error. If the module requires this library class, thecorresponding library instance mapping must be added into the[LibraryClasses] section of the DSC file.3.8 Debugging a <strong>Module</strong>The following steps are required before starting to debug a module.• “Build –b DEBUG” command<strong>EDK</strong> <strong>II</strong> supports generating DEBUG/RELEASE target. A different targetcauses different build options. The "BuildTarget" field in target.txt workswith the “ToolChain” field to determine the actual path of the compilertool-chain and build option. Developers can directly open$(WORKSPACE)\Conf\target.txt and change "TARGET = DEBUG" for thedebug tip. Developers also can use the command line to override thisvalue, such as "build -b DEBUG" for debug tip.• Choose the proper DebugLib library instance45

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!