BaseTools/ReadMe.txt

   1 This directory contains the next generation of EDK II build tools and template files.
   2 Templates are located in the Conf directory, while the tools executables for
   3 Microsoft Windows 32-bit Operating Systems are located in the Bin\Win32 directory.
   4
   5 The binary tools will be updated only after passing developer testing.
   6
   7 The BaseTools package will be updated with new tools only after all testing on a set
   8 of binary tools has successfully completed.
   9
  10 Current state of the tools is Proto-Type - not all tool functions have been implemented
  11 and there may be bugs in these tools.  These tools are under constant development at
  12 this time.
  13
  14 BaseTools Simple Usage:
  15 1) Change the directory to the EDK2 root directory, where the edksetup.bat is
  16 2) Run "edksetup.bat NewBuild"
  17 3) Set the ACTIVE_PLATFORM to your desired platform description file
  18    (%WORKSPACE%\Conf\target.txt)
  19 4) To build platform, run "build" command in non-module directory
  20 5) To build module individually, run "build" command in module directory, i.e. where the
  21    *.inf file is
  22
  23 Notes:
  24 1) Only *.efi files can be generated. Flash image cannot be generated at present.
  25 2) Only "clean" and "cleanall" build target are supported, in both top level
  26    makefile and module's makefile.
  27 3) Not all tool chains and target architectures are tested. Due to both tools
  28    and source code limitations, ther must be bugs in it. Please report any issue
  29          ASAP so we can fix it soon.
  30 4) The tree structure generated by build tools is similar to Ant build system.
  31 5) Makefile can be called directly by nmake for both top level platform and module. But
  32    after you call "nmake cleanall", you have to call "build" command to rebuild platform
  33          or modules because the AutoGen.* files have been be removed. The "makefile" itself
  34          cannot generate AutoGen.* files. Only "build" command can.
  35
  36
  37 Brief usage for Module Migration Tool msa2inf.exe:
  38 1. Command line format:
  39   msa2inf [options]
  40 2. Input Files:
  41   A syntactically valid MSA file
  42 3. Output Files:
  43   An extended INF file with possible auto-generated EntryPoint.c, CommonHeader.h/CommonHeader.txt, depending on options and module contents.
  44 4. Prerequisite:
  45    a. The workspace directory must be specified either by environment variable or \96w option.
  46    b. The Framework Database file must exist to specify the available packages in current workspace.
  47       Two possible locations are: (The first location overrides the second)
  48             $(WORKSPACE)\Tools\Conf\FrameworkDatabase.db
  49             $(WORKSPACE)\Conf\FrameworkDatabase.db.
  50       The <PackageList> field in FrameworkDatabase.db lists all available packages in current workspace.
  51       One example:
  52       <PackageList>
  53         <Filename>MdePkg/MdePkg.nspd</Filename>
  54         <Filename>MdeModulePkg/MdeModulePkg.spd</Filename>
  55         <Filename>IntelFrameworkPkg/IntelFrameworkPkg.spd</Filename>
  56       </PackageList>
  57       The package list in FrameworkDatabase.db is important to the final quality of migration:
  58       (1) It suggests the new package location: Translate package dependency Guid in MSA to Workspace relative path.
  59          If the package dependency Guid cannot be found in current workspace a warning message is raised.
  60       (2) It collects the Protocol/Guid/Ppi GuidCName a package contains.
  61          The GuidCName acts as "clue" to add e.g. #include <Protocol/DiskIo.h> in CommonHeader.h
  62
  63 5. Example:
  64    WORKSAPCE has already been set: $(WORKSPACE) = c:\work\EdkII.
  65
  66    a. msa2inf \96f c:\work\EdkII\Nt32Pkg\WinNtThunkDxe\WinNtThunk.msa \96o c:\work\EdkII\Nt32Pkg\WinNtThunkDxe\WinNtThunk.inf
  67    b. msa2inf \96f c:\work\EdkII\Nt32Pkg\WinNtThunkDxe\WinNtThunk.msa \96a
  68    Example a & b are equivalent to migrate WinNtThunk driver from EDKII to EDKII' code base.
  69
  70    c. msa2inf \96f c:\work\EdkII\Nt32Pkg\WinNtThunkDxe\WinNtThunk.msa \96a -c
  71    The extra "-c" option performs several hardcode mapping due to the naming change in EDKII\92:
  72       OldMdePkg Guid -> MdePkgGuid,
  73       EdkModulePkg Guid -> MdeModulePkgGuid,
  74       EdkGraphicsLib -> GraphicsLib
  75       HiiLib -> HiiLibFramework
  76       ...
  77
  78    d. msa2inf \96f c:\work\EdkII\Nt32Pkg\WinNtThunkDxe\WinNtThunk.msa \96m
  79    The extra "-m" option suppresses the generation of "CommonHeader.h" and leave all C files intact.
  80    Instead, it generates "CommonHeader.txt". Developers can manually copy its content to a local common header file in a module.
  81
  82 6. Known Limitations:
  83    a. Tool does not Exit Boot Services Callback & Virtual Address Changed Event. Developers need  to handle it manually.
  84    b. The #include <Library/AbcLib.h> is based on library class naming convention: The header filename for "AbcLib" class are "AbcLib.h" by convention.
  85    c. The #include <Guid/Xyz.h>, <Protocol/Xyz.h> and <Ppi/Xyz.h> are added based on gGuidCName listed in MSA.
  86       If a GuidCName cannot map to a package Guid/Protocol/Ppi header file, a warning message is raised.
  87       If a module uses the definition in a pakcage Guid/Protocol/Ppi header file without list its associative GuidCName, the build will beak. Developer needs to       manually add the include statement.
  88    d. The [Depex] sections are generated from DXS files with Guid Macro translated to Guid CName by naming convention, etc.
  89     If tool fails to "guess" the Guid CName from Guid Macro, it will leave the GuidMacro in [Depex] section for manual resolution.
  90    e. When tool generates [Sources] section, the modifiers for source files are lost. (Need to add proper tool chain, etc)
  91    f. When tool generates [LibraryClasses] section, the recommended library instances are lost. (No impact to build)
  92
  93
  94
  95 13-August-2007