[mirror_edk2.git] / 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.
5 The binary tools will be updated only after passing developer testing.
7 The BaseTools package will be updated with new tools only after all testing on a set
8 of binary tools has successfully completed.
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.
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
23 Notes:
24 1) The tree structure generated by build tools is similar to Ant build system.
25 2) Makefile can be called directly by nmake for both top level platform and module. But
26 after you call "nmake cleanall", you have to call "build" command to rebuild platform
27 or modules because the AutoGen.* files have been be removed. The "makefile" itself
28 cannot generate AutoGen.* files. Only "build" command can.
29 3) build.exe in %WORKSPACE%\BaseTools\Bin\Win32 is generated from following revision of
30 Python source code:
31 r641 <buildtools_project>\BaseTools\Source\Python\Autogen
32 r641 <buildtools_project>\BaseTools\Source\Python\build
33 r641 <buildtools_project>\BaseTools\Source\Python\Common
34 r641 <buildtools_project>\BaseTools\Source\Python\CommonDataClass
35 r564 <buildtools_project>\BaseTools\Source\Python\GenFds
36 4) GenFds.exe has is a combo of the follow python source.(This is a temporary branch)
37 r641 <buildtools_project>\BaseTools\Source\Python\Common
38 r641 <buildtools_project>\BaseTools\Source\Python\CommonDataClass
39 r564 <buildtools_project>\BaseTools\Source\Python\GenFds
41 Brief usage for Migration Tool MigrationMsa2Inf.exe:
42 1. Command line format:
43 MigrationMsa2Inf [options]
44 2. Input Files:
45 A syntactically valid MSA file
46 3. Output Files:
47 An extended INF file with possible auto-generated EntryPoint.c, CommonHeader.h/CommonHeader.txt, depending on options and module contents.
48 4. Prerequisite:
49 a. The workspace directory must be specified either by environment variable or -w option.
50 b. The Framework Database file must exist to specify the available packages in current workspace.
51 Two possible locations are: (The first location overrides the second)
52 $(WORKSPACE)\Tools\Conf\FrameworkDatabase.db
53 $(WORKSPACE)\Conf\FrameworkDatabase.db.
54 The <PackageList> field in FrameworkDatabase.db lists all available packages in current workspace.
55 One example:
56 <PackageList>
57 <Filename>MdePkg/MdePkg.nspd</Filename>
58 <Filename>MdeModulePkg/MdeModulePkg.spd</Filename>
59 <Filename>IntelFrameworkPkg/IntelFrameworkPkg.spd</Filename>
60 </PackageList>
61 The package list in FrameworkDatabase.db is important to the final quality of migration:
62 (1) It suggests the new package location: Translate package dependency Guid in MSA to Workspace relative path.
63 If the package dependency Guid cannot be found in current workspace a warning message is raised.
64 (2) It collects the Protocol/Guid/Ppi GuidCName a package contains.
65 The GuidCName acts as "clue" to add e.g. #include <Protocol/DiskIo.h> in CommonHeader.h
67 5. Example:
68 WORKSAPCE has already been set: $(WORKSPACE) = c:\work\EdkII.
70 a. MigrationMsa2Inf -f c:\work\EdkII\Nt32Pkg\WinNtThunkDxe\WinNtThunk.msa -o c:\work\EdkII\Nt32Pkg\WinNtThunkDxe\WinNtThunk.inf
71 b. MigrationMsa2Inf -f c:\work\EdkII\Nt32Pkg\WinNtThunkDxe\WinNtThunk.msa -a
72 Example a & b are equivalent to migrate WinNtThunk driver from EDKII to EDKII' code base.
74 c. MigrationMsa2Inf -f c:\work\EdkII\Nt32Pkg\WinNtThunkDxe\WinNtThunk.msa -a -c
75 The extra "-c" option performs several hardcode mapping due to the naming change in EDKII':
76 OldMdePkg Guid -> MdePkgGuid,
77 EdkModulePkg Guid -> MdeModulePkgGuid,
78 EdkGraphicsLib -> GraphicsLib
79 HiiLib -> HiiLibFramework
80 ...
82 d. MigrationMsa2Inf -f c:\work\EdkII\Nt32Pkg\WinNtThunkDxe\WinNtThunk.msa -m
83 The extra "-m" option suppresses the generation of "CommonHeader.h" and leave all C files intact.
84 Instead, it generates "CommonHeader.txt". Developers can manually copy its content to a local common header file in a module.
86 6. Known Limitations:
87 a. Tool does not handle Exit Boot Services Callback & Virtual Address Changed Event. Developers need to handle it manually.
88 b. The #include <Library/AbcLib.h> is based on library class naming convention: The header filename for "AbcLib" class are "AbcLib.h" by convention.
89 c. The #include <Guid/Xyz.h>, <Protocol/Xyz.h> and <Ppi/Xyz.h> are added based on gGuidCName listed in MSA.
90 If a GuidCName cannot map to a package Guid/Protocol/Ppi header file, a warning message is raised.
91 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.
92 d. The [Depex] sections are generated from DXS files with Guid Macro translated to Guid CName by naming convention, etc.
93 If tool fails to "guess" the Guid CName from Guid Macro, it will leave the GuidMacro in [Depex] section for manual resolution.
94 e. When tool generates [Sources] section, the modifiers for source files are lost. (Need to add proper tool chain, etc)
95 f. When tool generates [LibraryClasses] section, the recommended library instances are lost. (No impact to build)
97 7. Pyton Source
98 r633 <buildtools_project>\BaseTools\Source\Python\MigrationMsa2Inf
101 Brief Usage for PcdSyntax Update:
102 Usage:
103 PcdSyntaxUpdate.exe <directory_name>
104 It searches all INF, DEC and DSC file under <directory_name> and update them with the following rules:
105 1. Update INF files to conform to INF spec 0.44:
106 a. Rename PCD section name: e.g. [PcdsFeatureFlag] -> [FeaturePcd]
107 b. Adjust PCD section item format: e.g. PcdDebugClearMemoryValue|gEfiMdePkgTokenSpaceGuid -> gEfiMdePkgTokenSpaceGuid.PcdDebugClearMemoryValue
108 c. Update the syntax of binary INF file (not PCD related)
109 2. Update DEC files to confirm to DEC spec 0.36
110 Adjust PCD section item format: e.g. PcdWinNtPhysicalDisk|0x00001000|gEfiNt32PkgTokenSpaceGuid|VOID*|L"E:RW;245760;512"-> gEfiNt32PkgTokenSpaceGuid.PcdWinNtFlashFvRecoverySize|0x0|UINT32|0x00001011
111 3. Update DSC files to confirm to DSC spec
112 a. Adjust string/array typed PCD item format: e.g. PcdWinNtMemorySizeForSecMain|gEfiNt32PkgTokenSpaceGuid|L"64!64"|12 -> gEfiNt32PkgTokenSpaceGuid.PcdWinNtMemorySizeForSecMain|L"64!64"|VOID*|12
113 b. Adjust non-string/array typed PCD item format: e.g. PcdWinNtBootMode|gEfiNt32PkgTokenSpaceGuid|1 -> gEfiNt32PkgTokenSpaceGuid.PcdWinNtBootMode|1
114 c. Update the override library class in [Components] section: e.g.
115 <LibraryClass> {
116 PcdLib|MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf
117 }
118 To
119 <LibraryClasses> {
120 PcdLib|MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf
121 }
123 30-August-2007