Add comments in DSC files to explain the function and design of components section.

git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@7488 6f19259b-4bc3-4df7-8a09-765794883524
This commit is contained in:
xli24 2009-02-10 08:55:56 +00:00
parent 6074a6fb4b
commit b2ba1c1e2b
1 changed files with 18 additions and 0 deletions

View File

@ -131,6 +131,24 @@ define GCC_MACRO = -DEFI_SPECIFICATION_VERSION=0x00020000 -DPI_S
MSFT:*_*_IPF_APP_FLAGS = /D EFI64 $(MSFT_MACRO)
MSFT:*_*_IPF_PP_FLAGS = /D EFI64 $(MSFT_MACRO)
###################################################################################################
#
# Components Section - list of the modules and components that will be processed by compilation
# tools and the EDK II tools to generate PE32/PE32+/Coff image files.
#
# Note: The EDK II DSC file is not used to specify how compiled binary images get placed
# into firmware volume images. This section is just a list of modules to compile from
# source into UEFI-compliant binaries.
# It is the FDF file that contains information on combining binary files into firmware
# volume images, whose concept is beyond UEFI and is described in PI specification.
# Binary modules do not need to be listed in this section, as they should be
# specified in the FDF file. For example: Shell binary (Shell_Full.efi), FAT binary (Fat.efi),
# Logo (Logo.bmp), and etc.
# There may also be modules listed in this section that are not required in the FDF file,
# When a module listed here is excluded from FDF file, then UEFI-compliant binary will be
# generated for it, but the binary will not be put into any firmware volume.
#
###################################################################################################
[Components.Common]